Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Command failed: npm run build #1189

Closed
Arrk-SonaliBapte opened this issue Apr 2, 2024 · 3 comments · Fixed by #1191
Closed

Error: Command failed: npm run build #1189

Arrk-SonaliBapte opened this issue Apr 2, 2024 · 3 comments · Fixed by #1191
Assignees
Labels
bug Something isn’t working

Comments

@Arrk-SonaliBapte
Copy link

Arrk-SonaliBapte commented Apr 2, 2024

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
@Arrk-SonaliBapte Arrk-SonaliBapte added the bug Something isn’t working label Apr 2, 2024
@Fil
Copy link
Contributor

Fil commented Apr 2, 2024

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).

@mbostock
Copy link
Member

mbostock commented Apr 2, 2024

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).

@mbostock mbostock self-assigned this Apr 2, 2024
@mbostock
Copy link
Member

mbostock commented Apr 2, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn’t working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants