Revert "Synchronise package with module template (July 2023) (#98)"

[legobeat]

This reverts commit ab0ebca (#98).

As #98 removes the ability to import or require from paths like
@metamask/rpc-errors/dist/foo and a release is still pending for the
current major, this will have to be temporarily reverted.

After a 5.x release has been made addressing #100 , this change can be reintroduced.

Related:

• types: Make Data type-parameter optional in JsonRpcError #102
• Provide compatible types for v5.x #100
• 6.0.0 #99
• Synchronise package with module template (July 2023) #98

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
fast-deep-equal	2.0.1	None	+0	5.42 kB	esp
eslint-plugin-node	11.1.0	filesystem	+1	427 kB	mysticatea
@metamask/auto-changelog	3.2.0...2.6.1	environment	+0/-0	150 kB	gudahtt
@metamask/eslint-config-jest	12.1.0...11.1.0	None	+2/-29	3.68 MB	metamaskbot
@metamask/eslint-config-typescript	12.1.0...11.1.0	None	+2/-3	68.9 MB	metamaskbot
@metamask/eslint-config-nodejs	12.1.0...11.1.0	None	+3/-7	640 kB	metamaskbot
@metamask/eslint-config	12.1.0...11.1.0	None	+0/-1	118 kB	metamaskbot

🚮 Removed packages: @swc/[email protected], @swc/[email protected], @types/[email protected], [email protected], [email protected], [email protected], [email protected]

[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: @metamask/[email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]

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 package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

[legobeat]

@SocketSecurity ignore @metamask/[email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]