Automatic inclusion of package.json breaks Next SSG

[tjzel]

Description

After bumping react-native-builder-bob in Reanimated monorepo, our example app using Next stopped building with a very obscure error.

Errors screenshots

Obviously this file doesn't have any instances of global and it worked well before the bump.

After investigation turns out the culprit is enforced addition of package.json into the build directory added in

• fix: always create package.json with type regardless of esm option #598

I don't exactly understand why is that causing the error, especially that the error message and the callstack itself don't provide any useful information.

Packages

• create-react-native-library
• react-native-builder-bob

Selected options

 {    "source": "src",
    "output": "lib",
    "targets": [
      "module",
      "typescript"
    ]
  }

Link to repro

https://github.com/software-mansion/react-native-reanimated/tree/main/apps/next-example

Environment

Irrelevant, since it breaks in GitHub actions as well.

[tjzel]

Hey @satya164, thanks for the quick release! I tested it and unfortunately the inclusion of package.json with "type":"commonjs" still breaks Next 😢

Also, using the following config:

{
    "source": "src",
    "output": "lib",
    "targets": [
      [
        "module",
        {
          "esm": true
        }
      ],
      "typescript"
    ]
}

results in the same error as in the original issue.

[satya164]

@tjzel seems like this is a NextJS bug :<
type: commonjs should behave exactly like having no type. without this there is no way to support specifying type: module in root package.json. we can temporarily remove the package.json but it's not a permanent solution.

[satya164]

results in the same error as in the original issue.

When ESM option is enabled, afaik it's necessary to use globalThis instead of global since global is a legacy thing.

[tjzel]

I replaced all uses of global in Reanimated with globalThis, even though files using global shouldn't be loaded into the Next example, and the issue persists. It must be something very eerie about Next/Webpack.

Thank you for the 0.30.2 version, with esm: true it works now as before 🥳