You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Isomorphic-fetch is no longer being maintained and is causing a deprecation warning on node v22.11.0 by pulling in punycode.
From the zkapp-cli:
> node --trace-deprecation src/bin/index.js project test
? Create an accompanying UI project too? … (node:2145) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
at node:punycode:3:9
at BuiltinModule.compileForInternalLoader (node:internal/bootstrap/realm:399:7)
at BuiltinModule.compileForPublicLoader (node:internal/bootstrap/realm:338:10)
at loadBuiltinModule (node:internal/modules/helpers:114:7)
at Function._load (node:internal/modules/cjs/loader:1100:17)
at TracingChannel.traceSync (node:diagnostics_channel:315:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:218:24)
at Module.require (node:internal/modules/cjs/loader:1340:12)
at require (node:internal/modules/helpers:141:16)
at Object.<anonymous> (zkapp-cli/node_modules/whatwg-url/lib/url-state-machine.js:2:18)
> npm ls whatwg-url
[email protected]
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└── [email protected]
When this is done, remove the whatwg-url version override from zkapp-cli's package.json o1-labs/zkapp-cli#707
The text was updated successfully, but these errors were encountered:
yup, and we can simply remove isomorphic-fetch because all it does is add a shim for fetch() in node versions lower than 18. In node >= 18, fetch() is a builtin global that we should be able to use directly. I don't think we care about lower node versions anymore
Isomorphic-fetch is no longer being maintained and is causing a deprecation warning on node v22.11.0 by pulling in punycode.
From the zkapp-cli:
When this is done, remove the whatwg-url version override from zkapp-cli's package.json o1-labs/zkapp-cli#707
The text was updated successfully, but these errors were encountered: