repro: [email protected] causes errors for repos with moduleResolution set to Node{16,Next}

[MajorLift]

Explanation

The changes introduced in superstruct v2.0.0-0 don't enable us to go back to using superstruct.

To demonstrate, I created a repro branch where all dependencies and nested dependencies are forced to use superstruct v2.0.0-0 via yarn resolutions.

In the ci build run results, we still see a large number of the following error for type imports when Node{16,Next} is enabled:

error TS1479: The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'.

https://github.com/MetaMask/core/actions/runs/9654219968/job/26628058963?pr=4458

The reason for this is that our libraries are CJS and superstruct is ESM, and with Node{16,Next} enabled, a CJS project can only import types from an ESM project if it exports type declarations files that are unambiguously specified as .d.cts. Ambiguous .ts and .d.ts files that are interoperable between CJS/ESM are no longer supported in Node{16,Next}.

• See also: Fix ESM/CJS compatibility superstruct#1, Cannot use this in a project with module and moduleResolution of nodenext/node16 utils#163.

References

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/@aashutoshrathi/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@eslint-community/[email protected], npm/@jridgewell/[email protected], npm/@lavamoat/[email protected], npm/@lavamoat/[email protected], npm/@metamask/[email protected], npm/@noble/[email protected], npm/@npmcli/[email protected], npm/@npmcli/[email protected], npm/@npmcli/[email protected], npm/@npmcli/[email protected], npm/@scure/[email protected], npm/@scure/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@vue/[email protected], npm/@vue/[email protected], npm/@vue/[email protected], npm/@vue/[email protected], npm/@vue/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

[MajorLift]

@SocketSecurity ignore-all