-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
esm: Bug in dynamic modules refactoring #25482
Comments
This issue is also happening in the 10 LTS version, breaking in 10.15.3. See #26595. |
I can confirm, we got the same error when trying to update from 10.15.1 to 10.15.3. |
This also triggers the bug (Node.js v10.15.2 ok, v10.15.3 buggy): import blockchainWalletService from 'blockchain-wallet-service' See #25310 (comment). |
Was hoping there would be some progress with 12.x release. Are there any plans to fix it in the near future? |
I am able to reproduce the bug, I think I am able to isolate it: https://github.com/nodejs/node/pull/27443/files Steps to reproduce: Unfortunately I didn't find a successful fix, I feel I don't have enough experience on the CJS loader to understand the bug. I am leaving my test available for anyone who wants to work on that. |
This test shows the regression introduced in v11.4.0: clearing out the require.cache crashes node when using the `--experimental-modules` flag. Refs: nodejs#25482
This issue is also happening in the |
Also happening in the |
This test shows the regression introduced in v11.4.0: clearing out the require.cache crashes node when using the `--experimental-modules` flag. Refs: #25482 PR-URL: #25491 Reviewed-By: Guy Bedford <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Fixes: #25482 PR-URL: #25491 Reviewed-By: Guy Bedford <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
This test shows the regression introduced in v11.4.0: clearing out the require.cache crashes node when using the `--experimental-modules` flag. Refs: #25482 PR-URL: #25491 Reviewed-By: Guy Bedford <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Fixes: #25482 Backport-PR-URL: #27874 PR-URL: #25491 Reviewed-By: Guy Bedford <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
This test shows the regression introduced in v11.4.0: clearing out the require.cache crashes node when using the `--experimental-modules` flag. Refs: #25482 Backport-PR-URL: #27874 PR-URL: #25491 Reviewed-By: Guy Bedford <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Fixes: nodejs/node#25482 PR-URL: nodejs/node#25491 Reviewed-By: Guy Bedford <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
This test shows the regression introduced in v11.4.0: clearing out the require.cache crashes node when using the `--experimental-modules` flag. Refs: nodejs/node#25482 PR-URL: nodejs/node#25491 Reviewed-By: Guy Bedford <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Reposted from nodejs/help#1717.
Specs:
Linux HOSTNAME 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
--experimental-modules
request-promise-native
, but stacktrace also points topsl
and core node as suspect.Problem Statement:
Importing
request-promise-native
using ES6 module syntax on v11.4.0 or v11.5.0 causes a stacktrace which (I think) points to an error in core node:Steps To Reproduce:
nvm install v11.4.0
git clone https://gist.github.com/kj800x/f08f44305429bbf8fdd65f9991cb2a71 && cd f08f44305429bbf8fdd65f9991cb2a71
request-promise-native
and a package.json and a package-lock.jsonnpm i
npm start
nvm install v11.3.0
npm start
Related
The last three comments on this
request-promise-native
issue are related: request/request-promise-native#1 (comment)The text was updated successfully, but these errors were encountered: