[cloning template failed] npm init wasm-app
See original GitHub issueI just tried to create an instance of create-wasm-app
by executing npm init wasm-app
.
I was expecting the project initialization to succeed.
Instead, I got this error log:
~/Development/accept npm init wasm-app
npx: installed 1 in 2.048s
cloning the template failed!
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:16 (1 by maintainers)
Top Results From Across the Web
Tutorial: Conway's Game of Life in Rust and WebAssembly
npm init wasm -app www npx: installed 1 in 1.027s cloning the template failed! I see that this error message was added to...
Read more >failed to load wasm application - Stack Overflow
wasm file with .js scripts created by the wasm-pack tool. I tested the project locally with npm and node.js and everything worked fine....
Read more >Compiling from Rust to WebAssembly - MDN Web Docs
This tutorial takes you through all you need to know to compile a Rust project to wasm and use it in an existing...
Read more >Rust And WebAssembly - wasm-pack
wasm -pack makes JavaScript, Rust based WebAssembly applications should be interoperable ... The above command download, compile, and install the wasm-pack .
Read more >Host and deploy ASP.NET Core Blazor WebAssembly
js ) fails, try using the unminified version ( decode.js ) instead. Update the app to use the decoder. In the wwwroot/index.html file,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
apparently you’re supposed to provide the project name as an argument to
npm init
, eg.:That seems to work fine, relevant code below:
Should we update the docs accordingly in order to reflect that? I can send a quick PR.
FWIW, I don’t think that’s the core issue, since I’ve have never had git configured to use a proxy.
Given the fact that this bug has existed since 2018 and still isn’t fixed, I have to disagree with that assessment. It may look simple, but if it really was then the issue would have been fixed long ago. Rather it looks like there’s some subtleties that are being overlooked somehow.
It also reminds me of the recently-introduced term builder gloves.