Fix Node.js v18+ compatibility

[legobeat]

• ci: Add Node.js v18 and v20 to versions being tested
• Fix compatibility with Node.js v18, v20

Blocked by / Depends on:

• devDeps: bump @metamask/eslint-config* from v9 to ^12.1.0 #90

Unblocks

• Remove support for Node.js 14 #91
  • deps: Update eth-json-rpc and metamask packages #95
    • 9.0.0 #96
      • deps: Bump @metamask/{eth-json-rpc-provider,rpc-errors}  core#1653
        • deps: Update @metamask/utils and @metamask/rpc-errors  snaps#1728

[socket-security]

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

Packages	Version	New capabilities	Transitives	Size	Publisher
eslint-plugin-promise	6.1.1	None	+5	2.78 MB	eslint-community-bot
eslint-plugin-n	15.7.0	filesystem	+9	3.39 MB	weiran.zsd
@metamask/eslint-config-jest	9.0.0...12.1.0	None	+70/-86	95.7 MB	metamaskbot
@metamask/eslint-config-typescript	9.0.1...12.1.0	None	+69/-85	95.3 MB	metamaskbot
typescript	4.4.4...4.8.4	None	+0/-0	68.8 MB	typescript-bot
@metamask/eslint-config-nodejs	9.0.0...12.1.0	None	+61/-78	22.7 MB	metamaskbot
@metamask/eslint-config	9.0.0...12.1.0	None	+57/-75	22.1 MB	metamaskbot
@typescript-eslint/eslint-plugin	4.33.0...5.62.0	None	+15/-50	75.9 MB	jameshenry
@typescript-eslint/parser	4.33.0...5.62.0	None	+10/-47	72.9 MB	jameshenry
eslint-plugin-prettier	3.4.1...4.2.1	None	+6/-43	14 MB	jounqin
eslint-plugin-jsdoc	36.1.1...43.0.7	None	+9/-47	5.17 MB	gajus
prettier	2.6.1...2.8.8	environment	+0/-0	11.2 MB	prettier-bot
eslint-plugin-import	2.25.4...2.28.1	None	+48/-66	8.22 MB	ljharb
eslint-plugin-jest	24.7.0...27.2.3	None	+17/-51	76.3 MB	simenb

🚮 Removed packages: [email protected], [email protected]

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Obfuscated require	eslint-plugin-es	4.1.0	Location: lib/configs/restrict-to-es2015.js +27 more instances...	@metamask/[email protected], [email protected] via package.json
Obfuscated require	resolve	1.22.4	Location: test/resolver_sync.js +1 more instances...	@metamask/[email protected], @metamask/[email protected], @metamask/[email protected], @metamask/[email protected], [email protected], [email protected], [email protected] via package.json

Ignoring: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]

Next steps

What is obfuscated require?

Package accesses dynamic properties of require and may be obfuscating code execution.

The package should not access dynamic properties of module. Instead use import or require directly.

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

• @SocketSecurity ignore [email protected]
• @SocketSecurity ignore [email protected]

[legobeat]

@SocketSecurity ignore [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]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]
@SocketSecurity ignore [email protected]

[legobeat]

This is resolved as of #90