No exports defined error with Next.js TS config

[victorteokw]

When use this with Next.js TypeScript config, this module cannot be found.

By add one line in package.json fixes this problem.

  "exports": {
    ".": {
      "types": "./types/index.d.ts",
      "import": "./dist/index.mjs",
      "default": "./dist/index.mjs",
    }
  },

[slevithan]

See discussion on PR #8. Something in some people's pipeline is trying to load this module as CJS even though it's ESM only. Based on other people's experiences, using next.config.mjs instead of next.config.ts might fix the issue, as might upgrading Vite (to 5.x) or other build tools.

The fix suggested by @victorteokw above (adding default to exports) doesn't seem like the right one, since it will likely lead to some build tools trying to use the ESM module as CJS.

Whatever the underlying issue is likely needs to be reported and fixed in other tools, but I'm open to other suggestions for how package.json could be updated to work around the problem.

[wisdomstar94]

Next.js has recently started supporting next.config.ts.

The same thing happens to me when I use next.config.ts.

However, it works well with next.config.mjs without errors.

[slevithan]

This is assumed to be fixed by v2.0.0, which added a CommonJS bundle.