Open cowwoc opened 3 weeks ago
I can repro this with:
pulumi new kubernetes-typescript
...
pulumi preview
Modifying Pulumi.yaml
to trace node warnings:
name: npunyk8s
runtime:
name: nodejs
options:
packagemanager: npm
nodeargs: --trace-warnings
And running pulumi preview
again:
(node:38212) [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:113:7)
at Function._load (node:internal/modules/cjs/loader:1097:17)
at TracingChannel.traceSync (node:diagnostics_channel:322:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:216:24)
at Module.require (node:internal/modules/cjs/loader:1337:12)
at require (node:internal/modules/helpers:139:16)
at Object.<anonymous> (/Users/user/npunyk8s/node_modules/whatwg-url/lib/url-state-machine.js:2:18)
Looking at my package-lock.json
, it looks like whatwg-url
is a dependency of node-fetch
:
"node_modules/node-fetch": {
"version": "2.7.0",
"resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-2.7.0.tgz",
"integrity": "sha512-c4FRfUm/dbcWZ7U+1Wq0AwCyFL+3nt2bEw05wfxSz+DWpWsitgmSgYmy2dQdWyKC1694ELPqMs/YzUSNozLt8A==",
"license": "MIT",
"dependencies": {
"whatwg-url": "^5.0.0"
},
Which is a dependency of @pulumi/kubernetes
:
Transferring this issue to https://github.com/pulumi/pulumi-kubernetes
Same, this message comes every time you run pulumi
command - so annoying. Any workaround for now?
Looking at the repo, it seems like node-fetch
is not even used anywhere in the codebase 🤔
Looking at the repo, it seems like
node-fetch
is not even used anywhere in the codebase 🤔
It is used
but should just be a matter of updating the dependency.
What happened?
Every time
pulumi
is run, it outputs:Example
Run
pulumi up
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).