[ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in package.json #382

borkdude · 2022-04-13T18:29:29Z

Nbb, a ClojureScript interpreter for Node.js uses dynamic import to load libraries. To resolve which JS file to load, it uses code like the following:

import { createRequire } from 'module';

const req = createRequire(import.meta.url);

console.log(req.resolve('zx'));

This code worked in zx 5.3.0 but stopped working in 6.0.7 with the following error:

$ node script.mjs
path
node:internal/errors:465
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in /private/tmp/test-nbb/node_modules/zx/package.json
    at new NodeError (node:internal/errors:372:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:433:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:657:7)
    at resolveExports (node:internal/modules/cjs/loader:482:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:919:27)
    at Function.resolve (node:internal/modules/cjs/helpers:108:19)
    at file:///private/tmp/test-nbb/script.mjs:6:17
    at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
    at async Promise.all (index 0) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

The text was updated successfully, but these errors were encountered:

antonmedv · 2022-04-13T18:48:40Z

Can't tell what is wrong.

antonmedv · 2022-04-13T18:49:01Z

No looking as zx issue,

borkdude · 2022-04-13T19:01:20Z

@antonmedv The structure of package.json did change between 5.3.0 and 6.0.0, could it have something to do with that?

antonmedv · 2022-04-13T19:19:09Z

IDK

antonmedv · 2022-04-15T12:10:52Z

Can't repoduce.

borkdude · 2022-04-15T12:14:56Z

What did you try to reproduce? Here is a detailed reproduction using Node 14 and Node 17:

borkdude@MBP2019 /tmp $ mkdir zxtest
borkdude@MBP2019 /tmp $ cd zxtest
borkdude@MBP2019 /tmp/zxtest $ npm install zx
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'zx@6.1.0',
npm WARN EBADENGINE   required: { node: '>= 16.0.0' },
npm WARN EBADENGINE   current: { node: 'v14.18.0', npm: '8.5.4' }
npm WARN EBADENGINE }

added 52 packages, and audited 53 packages in 3s

9 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
borkdude@MBP2019 /tmp/zxtest $ cat package.json
{
  "dependencies": {
    "zx": "^6.1.0"
  }
}
borkdude@MBP2019 /tmp/zxtest $ cat index.mjs
import { createRequire } from 'module';

const req = createRequire(import.meta.url);

console.log(req.resolve('zx'));
borkdude@MBP2019 /tmp/zxtest $ node index.mjs
internal/process/esm_loader.js:74
    internalBinding('errors').triggerUncaughtException(
                              ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in /private/tmp/zxtest/node_modules/zx/package.json
    at new NodeError (internal/errors.js:322:7)
    at throwExportsNotFound (internal/modules/esm/resolve.js:322:9)
    at packageExportsResolve (internal/modules/esm/resolve.js:511:7)
    at resolveExports (internal/modules/cjs/loader.js:450:36)
    at Function.Module._findPath (internal/modules/cjs/loader.js:490:31)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:888:27)
    at Function.resolve (internal/modules/cjs/helpers.js:99:19)
    at file:///private/tmp/zxtest/index.mjs:5:17
    at ModuleJob.run (internal/modules/esm/module_job.js:183:25)
    at async Loader.import (internal/modules/esm/loader.js:178:24) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}
borkdude@MBP2019 /tmp/zxtest $ node --version
v14.18.0
borkdude@MBP2019 /tmp/zxtest $ nvm use 17
Now using node v17.8.0 (npm v8.5.5)
borkdude@MBP2019 /tmp/zxtest $ node --version
v17.8.0
borkdude@MBP2019 /tmp/zxtest $ node index.mjs
node:internal/errors:465
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in /private/tmp/zxtest/node_modules/zx/package.json
    at new NodeError (node:internal/errors:372:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:448:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:672:7)
    at resolveExports (node:internal/modules/cjs/loader:482:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:919:27)
    at Function.resolve (node:internal/modules/cjs/helpers:108:19)
    at file:///private/tmp/zxtest/index.mjs:5:17
    at ModuleJob.run (node:internal/modules/esm/module_job:198:25)
    at async Promise.all (index 0) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Node.js v17.8.0

antonmedv · 2022-04-15T12:16:39Z

Node 14 not supported.

borkdude · 2022-04-15T12:17:34Z

It is also is reproducible using 16 and 17 (as shown above for 17).

antonmedv · 2022-04-15T12:18:58Z

Let me again

antonmedv · 2022-04-15T20:24:49Z

Debugged. zx does not provide CJS version starting with v6.

The error ERR_PACKAGE_PATH_NOT_EXPORTED, is thrown by using require() on zx. This is not supported by node. Use import().

You can try this:

console.log(await import.meta.resolve('zx'));

❯ node --experimental-import-meta-resolve index.mjs
file:///Users/anton/dev/zx-playground/node_modules/zx/src/index.mjs

borkdude · 2022-04-15T20:29:18Z

Thanks for debugging. I think it is supported as you can see in this ESM documentation:

https://nodejs.org/api/module.html#modulecreaterequirefilename

I am not calling require, I'm only using its resolve mechanism. It works on libraries like execa which are also ESM only.

Unfortunately I can't use import.meta.resolve.

antonmedv · 2022-04-15T20:44:40Z

It works on libraries like execa which are also ESM only.

Can't tell why zx does not work the same way. ¯_(ツ)_/¯

borkdude · 2022-04-15T21:10:59Z

Maybe we will one day figure it out, thanks for the time and help :).

borkdude · 2022-04-15T21:22:09Z

@antonmedv I may have found the issue. When I edit package.json in node_modules/zx and change the main export to:

  "exports": {
    ".": "./src/index.mjs",

it starts working. That seems more like the schema they describe here:

https://nodejs.org/api/packages.html#subpath-exports

antonmedv · 2022-04-15T21:25:00Z

I see. But we can't ditch types. Also conditional exports possible: https://nodejs.org/api/packages.html#conditional-exports which zx uses.

Two possible ways: maybe an issue in require.resolve? Or how to define types not in exports?

borkdude · 2022-04-15T21:26:47Z

You're right, I missed that. I'll file a bug with Node.js.

borkdude · 2022-04-15T21:30:29Z

Now I'm not sure if this is a Node.js bug either since when I add:

      "import": "./src/index.mjs",
      "require": "./src/index.mjs",

then it also works again. I guess I'm stuck for now then, until I can use import.meta.resolve.

borkdude · 2022-04-16T14:50:37Z

I can use https://github.com/wooorm/import-meta-resolve as a workaround.

borkdude · 2022-04-16T19:15:10Z

All fixed now, nbb 0.3.7 works with zx 6.0.0+:

(ns script
  (:require ["zx" :refer [$]]
            [nbb.core :refer [await]]))

(await ($ #js ["ls" "-la"]))
(prn :foo 1 2 3)

akefirad · 2022-04-18T05:36:31Z

Is there any workaround for this issue? (Why did the issue get closed?) I can reproduce the issue with the latest versions (node: 16.4.1, zx: v6.1.0). Thanks.

borkdude · 2022-04-18T07:00:25Z

@akefirad Can you make a repro? How are you using zx?

akefirad · 2022-04-19T05:20:52Z

There you go: zx-bug.zip. Forgot to mentioned I'm using it via ts-node. There's no custom code/configuration in the project whatsoever. Thanks.
Update: as other mentioned, version 4 works just fine.

LeonAlvarez · 2022-04-21T11:54:55Z

I confirm the same issue on the latest version, version 4.3 works fine

borkdude · 2022-04-21T11:55:52Z

@LeonAlvarez How are you using zx? Can you create a package.json + code sample?

idmyn · 2022-05-08T10:42:44Z

I've run into this issue trying to use zx with gatsby (which appears to have some trouble with ESM)

Are newer versions of zx incompatible with CommonJS format? If so, I wonder if that's worth flagging in the readme?

code sample: https://stackblitz.com/edit/node-rzx94p?file=index.js

vinayakkulkarni · 2022-05-09T08:17:58Z

node:internal/errors:464
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_REQUIRE_ESM]: require() of ES Module /app/node_modules/zx/index.mjs not supported.
Instead change the require of /app/node_modules/zx/index.mjs to a dynamic import() which is available in all CommonJS modules.
    at file:///app/build/scripts/start.mjs:3:23
    at async importPath (file:///app/node_modules/zx/zx.mjs:128:3)
    at async main (file:///app/node_modules/zx/zx.mjs:50:7)
    at async file:///app/node_modules/zx/zx.mjs:26:1 {
  code: 'ERR_REQUIRE_ESM'
}
npm notice
npm notice New major version of npm available! 7.21.0 -> 8.9.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.9.0
npm notice Run npm install -g npm@8.9.0 to update!
npm notice
node:internal/errors:464
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_REQUIRE_ESM]: require() of ES Module /app/node_modules/zx/index.mjs not supported.
Instead change the require of /app/node_modules/zx/index.mjs to a dynamic import() which is available in all CommonJS modules.
    at file:///app/build/scripts/start.mjs:3:23
    at async importPath (file:///app/node_modules/zx/zx.mjs:128:3)
    at async main (file:///app/node_modules/zx/zx.mjs:50:7)
    at async file:///app/node_modules/zx/zx.mjs:26:1 {
  code: 'ERR_REQUIRE_ESM'
}
node:internal/errors:464
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_REQUIRE_ESM]: require() of ES Module /app/node_modules/zx/index.mjs not supported.
Instead change the require of /app/node_modules/zx/index.mjs to a dynamic import() which is available in all CommonJS modules.
    at file:///app/build/scripts/start.mjs:3:23
    at async importPath (file:///app/node_modules/zx/zx.mjs:128:3)
    at async main (file:///app/node_modules/zx/zx.mjs:50:7)
    at async file:///app/node_modules/zx/zx.mjs:26:1 {
  code: 'ERR_REQUIRE_ESM'
}

Still facing this issue :(

antonmedv · 2022-05-09T08:21:46Z

require() of ES Module /app/node_modules/zx/index.mjs not supported.

cefn · 2022-05-20T09:54:56Z

In a reference repro this commit was enough to get a vanilla npm+typescript project to execute zx scripts with ts-node. More in the PR

akefirad · 2022-07-07T16:43:00Z

Hi team, is there any update regarding this issue? I appreciate that people might be busy with other stuff, but we were asked to provide sample code to reproduce it, but didn't get any reply. Thanks. 🙏

antonmedv closed this as completed Apr 15, 2022

borkdude mentioned this issue Apr 16, 2022

Enabling import meta resolve by default? nodejs/modules#550

Closed

cefn mentioned this issue May 20, 2022

ZX Removed CommonJS support, broke ts-node. cefn/zx-tsnode-repro#1

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in package.json #382

[ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in package.json #382

borkdude commented Apr 13, 2022 •

edited

Loading

antonmedv commented Apr 13, 2022

antonmedv commented Apr 13, 2022

borkdude commented Apr 13, 2022

antonmedv commented Apr 13, 2022

antonmedv commented Apr 15, 2022

borkdude commented Apr 15, 2022

antonmedv commented Apr 15, 2022

borkdude commented Apr 15, 2022

antonmedv commented Apr 15, 2022

antonmedv commented Apr 15, 2022 •

edited

Loading

borkdude commented Apr 15, 2022 •

edited

Loading

antonmedv commented Apr 15, 2022

borkdude commented Apr 15, 2022

borkdude commented Apr 15, 2022

antonmedv commented Apr 15, 2022

borkdude commented Apr 15, 2022

borkdude commented Apr 15, 2022

borkdude commented Apr 16, 2022

borkdude commented Apr 16, 2022 •

edited

Loading

akefirad commented Apr 18, 2022

borkdude commented Apr 18, 2022 via email •

edited

Loading

akefirad commented Apr 19, 2022 •

edited

Loading

LeonAlvarez commented Apr 21, 2022

borkdude commented Apr 21, 2022

idmyn commented May 8, 2022

vinayakkulkarni commented May 9, 2022

antonmedv commented May 9, 2022

cefn commented May 20, 2022

akefirad commented Jul 7, 2022

[ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in package.json #382

[ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in package.json #382

Comments

borkdude commented Apr 13, 2022 • edited Loading

antonmedv commented Apr 13, 2022

antonmedv commented Apr 13, 2022

borkdude commented Apr 13, 2022

antonmedv commented Apr 13, 2022

antonmedv commented Apr 15, 2022

borkdude commented Apr 15, 2022

antonmedv commented Apr 15, 2022

borkdude commented Apr 15, 2022

antonmedv commented Apr 15, 2022

antonmedv commented Apr 15, 2022 • edited Loading

borkdude commented Apr 15, 2022 • edited Loading

antonmedv commented Apr 15, 2022

borkdude commented Apr 15, 2022

borkdude commented Apr 15, 2022

antonmedv commented Apr 15, 2022

borkdude commented Apr 15, 2022

borkdude commented Apr 15, 2022

borkdude commented Apr 16, 2022

borkdude commented Apr 16, 2022 • edited Loading

akefirad commented Apr 18, 2022

borkdude commented Apr 18, 2022 via email • edited Loading

akefirad commented Apr 19, 2022 • edited Loading

LeonAlvarez commented Apr 21, 2022

borkdude commented Apr 21, 2022

idmyn commented May 8, 2022

vinayakkulkarni commented May 9, 2022

antonmedv commented May 9, 2022

cefn commented May 20, 2022

akefirad commented Jul 7, 2022

borkdude commented Apr 13, 2022 •

edited

Loading

antonmedv commented Apr 15, 2022 •

edited

Loading

borkdude commented Apr 15, 2022 •

edited

Loading

borkdude commented Apr 16, 2022 •

edited

Loading

borkdude commented Apr 18, 2022 via email •

edited

Loading

akefirad commented Apr 19, 2022 •

edited

Loading