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
for command npm init "@observablehq" on windows 11 with the latest node.js getting below error:
|
o Initialize git repository?
| Yes
|
o Initializing Framework cache...|
x Error: Command failed: npm run build
| (node:24144) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
| (Use `node --trace-deprecation ...` to show where the warning was created)
|
| Unexpected error: fetch failed
|
| Tip: To see the full stack trace, run with the --debug flag.
|
| If you think this is a bug, please file an issue at
| ↳ https://github.com/observablehq/framework/issues
|
|
|
• To see the full stack trace, run with the --debug flag.
│
│ If you think this is a bug, please file an issue at
└ https://github.com/observablehq/framework/issues
x Canceled
npm ERR! code 1
npm ERR! path C:\Users\sonalib
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c observablehq-create
npm ERR! A complete log of this run can be found in: C:\Users\sonalib\AppData\Local\npm-cache\_logs\2024-04-02T10_18_23_049Z-debug-0.log
The text was updated successfully, but these errors were encountered:
Can you run the command again with the --debug flag and report with the full stack trace? It seems that there was a network error (as indicated by fetch failed).
This is probably one of the data loaders failing during build. We should make this step optional; it should not cause create to fail (since you can always try again and we’re just trying to seed the cache here).
This is either a network configuration problem such as #1168 or a transient error that can be ignored. We will make this step optional and log a better warning.
for command
npm init "@observablehq"
on windows 11 with the latest node.js getting below error:The text was updated successfully, but these errors were encountered: