This repository has been archived by the owner on Aug 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 335
don't install wasm-pack for webpack projects #745
Comments
seems like crates.io may have had some down time or an incident when this happened. the real bug here is that it was attempting to install wasm-pack but it didn't need to be. this is similar to #768! @EverlastingBugstopper as you work on 768 can you also take a look at this? will be in the exact same part of the (bad) code (i wrote) :P |
Same issue here - a way to bypass wasm dependencies would be great (don't need them)
|
first attempt to do this in #849 didn't pan out. will try again with a new approach |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
π Bug Report
Environment
rustc -V
: rustc 1.38.0 (625451e37 2019-09-23)node -v
:wrangler -V
: π· β¨ wrangler 1.4.0Steps to reproduce
I have a static site generated from Hugo and am attempting to publish with Wrangler. It worked the first few times, but timed out trying to get to crates.io
What did you expect to see?
Publish success
What did you see instead?
Total in 30 ms C02WF0XWHV2R:blog-samrhea samrhea$ wrangler publish π Using namespace for Workers Site "__blog-samrhea-workers_sites_assets" π ignoring file .DS_Store π ignoring file .DS_Store π Uploading... β¨ Success β¬οΈ Installing wranglerjs... Error: https://crates.io/api/v1/crates/wasm-pack: error trying to connect: connect timed out
The text was updated successfully, but these errors were encountered: