8000 ES modules fail to be imported during node.js dynamic analysis · Issue #982 · ossf/package-analysis · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
ES modules fail to be imported during node.js dynamic analysis #982
@maxfisher-g

Description

@maxfisher-g

Around 2k NPM packages per day fail to be analyzed properly due to import errors:

The error messages are in 2 forms, for example:

  1. Failed to import @versini/ui-components: Error [ERR_REQUIRE_ESM]: require() of ES Module /app/node_modules/@versini/ui-components/dist/index.js from /usr/local/bin/analyze-node.js not supported.
  2. Failed to import isolate-package: Error [ERR_REQUIRE_ESM]: require() of ES Module /app/node_modules/isolate-package/dist/index.mjs not supported.

(the difference is that the first variant specifies from /usr/local/bin/analyze-node.js, and usually occurs when attempting to import an index.js file; the second variant is when importing .mjs files)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0