Still an issue for me whenever I upgrade SST

Error: There was a problem transpiling the Lambda handler: file:///Users/cyber/dev/jb/platform/packages/infra/.sst/artifacts/979b4130/builder.js:2
        const esbuild = require("esbuild")
                        ^

ReferenceError: require is not defined in ES module scope, you can use import instead
This file is being treated as an ES module because it has a '.js' file extension and '/Users/cyber/dev/jb/platform/packages/infra/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.
    at file:///Users/cyber/dev/jb/platform/packages/infra/.sst/artifacts/979b4130/builder.js:2:25
    at ModuleJob.run (internal/modules/esm/module_job.js:183:25)
    at async Loader.import (internal/modules/esm/loader.js:178:24)
    at async Object.loadESM (internal/process/esm_loader.js:68:5)

Trying to maintain this patch but it's not going great. I think I need to write package.json out to the

.sst

dir? Where do I get that path? What do we need to do to get this merged?

We have a lot of work to do to properly support ESM together with CJS across the board but we haven't prioritized that yet. For this issue you can probably write a

package.json

next to where that esbuild script is generated

ok thanks! i think this is working for me https://github.com/serverless-stack/serverless-stack/pull/1154/files

The latest version looks fairly minimal - do you think you can remove the package.json after it's built or no?

from both locations?

I was thinking just from the artifacts folder

done