镜像站点 · 本页由第三方 GitHub 只读镜像提供，非 GitHub 官方站点，不接受任何登录或凭据输入。前往 github.com
Skip to content

Errors from conditional exports after upgraded to Node 13.13 #32852

Closed
salesforce/akita
#447
Closed
Errors from conditional exports after upgraded to Node 13.13#32852
salesforce/akita
#447

Description

@JLHwung
JLHwung
opened on Apr 14, 2020
  • Version: Node.js 13.13
  • Platform: 19.4.0 Darwin Kernel Version 19.4.0
  • Subsystem: ES modules

What steps will reproduce the bug?

npm install @babel/compat-data
node -e "require('@babel/compat-data/corejs3-shipped-proposals')"

What is the expected behavior?

It should load the module as expected in Node.js 13.12

What do you see instead?

Error: Cannot find module '@babel/compat-data/corejs3-shipped-proposals'
Require stack:
- /tmp/[eval]
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:952:15)
    at Function.resolve (internal/modules/cjs/helpers.js:78:19)
    at [eval]:1:9
    at Script.runInThisContext (vm.js:131:20)
    at Object.runInThisContext (vm.js:297:38)
    at Object.<anonymous> ([eval]-wrapper:10:26)
    at Module._compile (internal/modules/cjs/loader.js:1123:30)
    at evalScript (internal/process/execution.js:94:25)
    at internal/main/eval_string.js:23:3 {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/tmp/[eval]' ]
}

Additional information

Caught by the Babel CI: https://travis-ci.com/github/babel/babel/jobs/319348116#L360

The regression was likely introduced in #32351.

The file structure of @babel/compat-data can be simplified w.l.o.g as

package.json
corejs3-shipped-proposals.js
data/corejs3-shipped-proposals.json

and the package.json:

"exports": {
  "./corejs3-shipped-proposals": "./data/corejs3-shipped-proposals.json"
}

The corejs3-shipped-proposals.js is a proxy which delegates to "./data/corejs3-shipped-proposals.json" for Node.js < 13.3 support.

module.exports = require("./data/corejs3-shipped-proposals.json");

Activity

  1. JLHwung commented on Apr 14, 2020

    @JLHwung
    JLHwung
    on Apr 14, 2020
    ContributorAuthor

    /cc @guybedford

  2. guybedford commented on Apr 14, 2020

    @guybedford
    guybedford
    on Apr 14, 2020
    Contributor

    @JLHwung I created babel/babel#11283 specifically to avoid Babel having this error. Was the above fix not patched and released already?

  3. JLHwung commented on Apr 14, 2020

    @JLHwung
    JLHwung
    on Apr 14, 2020
    ContributorAuthor

    @guybedford Ahh thanks. It was release in 7.9.0.

    For those babel users who are affected by this issue after upgrading to node.js 13.13/12.17, please upgrade @babel/preset-env to 7.9.0.

  4. JLHwung
    closed this as completedon Apr 14, 2020

  5. guybedford commented on Apr 14, 2020

    @guybedford
    guybedford
    on Apr 14, 2020
    Contributor

    Great, I'm glad the early fix here could help!

  6. michaelsbradleyjr
    added 3 commits that reference this issue on Apr 24, 2020

    build(deps): bump @babel/preset-env to >= 7.9.0

    f2ef50c

    build(deps): bump @babel/preset-env to >= 7.9.0

    32dc886

    build(deps): bump @babel/preset-env to >= 7.9.0

    44dfb99
  7. scottlamb
    added a commit that references this issue on May 9, 2020

    update all js deps

    ae5b840

  8. nandorojo commented on May 16, 2020

    @nandorojo
    nandorojo
    on May 16, 2020

    I had this problem in building a React Native Bob library. I solved it using nvm install 13.12, which downgraded my node to 13.12.

    This solution only applies if you use nvm to manage your Node versions (if you don't I recommend it!)

  9. PsychoLlama
    added a commit that references this issue on May 25, 2020

    Upgrade babel

    b6cac4c

  10. mamoonraja commented on May 28, 2020

    @mamoonraja
    mamoonraja
    on May 28, 2020

    FYI, I noticed the same issue in 12.17.x. We have to switch to 12.6.x in Travis for now.

  11. alex-mo
    added a commit that references this issue on Jun 2, 2020

    Update babel

    6afb7d6
  12. scjung
    added a commit that references this issue on Jun 6, 2020

    Upgrade @babel/preset-env to 7.9 for NodeJS 13.13.

    5bb8004
  13. alex-mo
    added a commit that references this issue on Jun 8, 2020

    campaignion_tracking: Update babel

    7394a72

  14. 2 remaining items

  15. CaptainAchab
    added a commit that references this issue on Jun 11, 2020

    chore(deps): bump @babel packages and regenerate yarn.lock

    0a45536
  16. maddalihanumateja
    added a commit that references this issue on Jun 16, 2020

    Updated npm packages

    3d14f5a
  17. stefanprobst
    added a commit that references this issue on Jun 20, 2020

    build: update @babel/preset-env to avoid nodejs/node#32852

    dcfdbd4
  18. tannerlinsley
    added a commit that references this issue on Jun 21, 2020

    feat: use react-query logo as toggle button (#37)

    dc0bdcb
  19. mehdisadeghi
    added a commit that references this issue on Jun 24, 2020

    Fix nodejs/node#32852

    7bab5c1
  20. mejackreed
    added a commit that references this issue on Jul 22, 2020

    This commit fixes an upstream issue with babel and node causing webpack

    2dc36b4
  21. cantino
    added a commit that references this issue on Jul 28, 2020

    Fix nodejs/node#32852

    236e0c9
  22. gruve-p
    added a commit that references this issue on Aug 2, 2020

    Build failed Travis (Cannot find module)

    72595bd
  23. thebaer
    added a commit that references this issue on Sep 9, 2020

    Fix webpack build issues

    70dbfcf
  24. jacobq
    added a commit that references this issue on Sep 21, 2020

    chore(deps): upgrade @babel/... for Node >12.x

    2f7ed03
  25. chriskrycho
    added a commit that references this issue on May 13, 2021

    Fix the build via new version of @babel/preset-env

    3fa42c0
  26. dabrady
    added a commit that references this issue on May 13, 2021

    upgrade(dep): babel/preset-env ^7.x -> ^7.9.0 for Node 13+ compat

    af20a26
  27. wincent
    added a commit that references this issue on Jul 6, 2021

    fix: update npm packages

    7a1d23a

  28. AndersDJohnson commented on Sep 17, 2021

    @AndersDJohnson
    AndersDJohnson
    on Sep 17, 2021

    Ran into similar problem, though on a later Node version and using yarn not npm, but this worked for me:

    yarn upgrade --scope @babel

  29. cluis13915 commented on Sep 3, 2024

    @cluis13915
    cluis13915
    on Sep 3, 2024

    Ran into similar problem, though on a later Node version and using yarn not npm, but this worked for me:

    yarn upgrade --scope @babel

    This worked for me. Thanks!

    ember-cli: 3.4.4
node: 12.22.12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions