-
Notifications
You must be signed in to change notification settings - Fork 828
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
Workbox Wizard breaks #1574
Comments
yupp m facing the same bug |
Apologies that you both are running into this. I tried to reproduce and I was not able to. I'm using PowerShell with node v8.11.3 installed, and the latest Also, can you reproduce it if you try running the wizard in a different directory? |
i noticed that because of nodejs version |
Okay, so this is pretty strange. I've installed I can't reproduce the issue when using the Git Bash shell on Windows, so I think this is particular to shells that use Windows-style paths. What seems to help is changing a few instances of asynchronous calls to their synchronous version. This gets a bit tricky, since the original source is transpiled with the regenerator runtime, to ensure that we support
is an example of one spot that causes hangs, and it progresses past that if I change the code locally to I'm going to debug more, and thanks for everyone's patience. |
Quick update—bumping the dependency versions for the various libraries used by |
@jeffposnick Any news on this? Facing the same issue and I see the PR is pending. |
Using Feel free to read the release notes and confirm that it's working for you now. |
I encountered this running Node v8.1.0. Using nvm, I switched to Node v8.9.0 and issue was resolved.
|
I'm using
I experienced the same issue listed by the OP but switching to |
Same issue here. Workbox-cli wizard stops at the first question
installing 4.0.0-beta.0 fixed everything. |
Library Affected:
workbox-cli
Browser & Platform:
Windows, Node
Issue:
workbox wizard
breaks at the 3rd prompt > Where would you like your service worker file to be saved?The text was updated successfully, but these errors were encountered: