I started getting this error after I updated the

sst

today to

1.2.9

Could not resolve "mock-aws-s3"

    node_modules/@mapbox/node-pre-gyp/lib/util/s3_setup.js:43:28:
      43 │     const AWSMock = require('mock-aws-s3');
         ╵                             ~~~~~~~~~~~~~

  You can mark the path "mock-aws-s3" as external to exclude it from the bundle, which will remove
  this error. You can also surround this "require" call with a try/catch block to handle this
  failure at run-time instead of bundle-time.

✘ [ERROR] Could not resolve "pg-native"

    node_modules/pg/lib/native/client.js:4:21:
      4 │ var Native = require('pg-native')
        ╵                      ~~~~~~~~~~~

  You can mark the path "pg-native" as external to exclude it from the bundle, which will remove
  this error. You can also surround this "require" call with a try/catch block to handle this
  failure at run-time instead of bundle-time.

✘ [ERROR] Could not resolve "nock"

    node_modules/@mapbox/node-pre-gyp/lib/util/s3_setup.js:112:23:
      112 │   const nock = require('nock');
          ╵                        ~~~~~~

  You can mark the path "nock" as external to exclude it from the bundle, which will remove this
  error. You can also surround this "require" call with a try/catch block to handle this failure at
  run-time instead of bundle-time.

when do you get these errors?

Today

haha no I meant do you get this during sst start? sst deploy?

When I hit an API endpoint which was working previously.

during sst start?

It was ^1.0.2 but now 1.2.9.

have you tried clearing node modules?

pg-native sounds like something you should exclude for esbuild

I tried reinstalling by removing the node modules and even tried by removing the stage completely, it is still giving the same error.

in an old serverless project I remember errors unless I used

esbuild:
    bundle: true
    packager: npm
    exclude: ['pg-native'] // <<--

@Klaus In which file should I add this?

the thing is if this is during sst start and was working before something seems off

new Function(stack, "MyLambda", {
  bundle: {
    externalModules: ["pg-native"],

try that above

@Klaus Tried that, it searches for

package.json

in that lamda directory.

@thdxr shouldn't the normal package.json be used by following the nodeJS config instructions for bundling

@Klaus Its actually another package that uses it.

I think in order to replicate the error, sharing your setup would be great for our friendly guys at SST😉 The error alone won't be enough to figure out why it happens