Not compatible with Webpack 5 (Next.js 11)

[Vadorequest]

Expected Behavior

Shouldn't log warnings

Current Behavior

When importing the file import { init } from '@amplitude/node';, it yields the following output:

warn  - ./node_modules/@amplitude/node/esm/src/constants.js
Should not import the named export 'version' (reexported as 'SDK_VERSION') from default-exporting module (only default export is available soon)

It's hard to tell if it's a warning or an error. The warning is displayed at every rebuild.

It seems to be related to webpack 5, the @amplitude/node package might not be compatible with Webpack 5. This affects Next.js 10+. (Webpack 5 is enabled by default in Next.js 11)

Steps to Reproduce

1. git clone [email protected]:UnlyEd/next-right-now.git nrn-refactor-amplitude && cd nrn-refactor-amplitude && git checkout refactor-amplitude && cp .env.local.example .env.local && yarn && yarn start
2. Go to localhost:8888/api/status and look at the server console

Environment

• SDK Version: "@amplitude/node": "1.6.1",
• Node version: v14

[yuhao900914]

cc: @ajhorst @jooohhn

[GabeMedrash]

For reference: https://webpack.js.org/migrate/5/#using-named-exports-from-json-modules

[ncailleux]

Still here, same warning with "@amplitude/node": "^1.9.2" & "next": "^12.1.0"

[wrgoto]

Any chance we can get an update on this to remove the warnings? It's really noisy.

[sbue]

+1

[MrtMonet]

is there any progress on this?

[alerafart]

Any answers on this one?

[PavelMeyer]

Any updates?

[phillipjacobs]

@PavelMeyer did you manage to resolve it. Same issue on my side.