Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to use Parcel (Windows x64)

See original GitHub issue

Discussed in https://github.com/parcel-bundler/parcel/discussions/7593

Parcel 2.2.1

** Expected Behavior ** Running npx parcel ./src/index.html to launch dev server.

** Actual Behavior** Running npx parcel ./src/index.html usually does nothing. A slight pause on the terminal before returning a new prompt. On rare occasion, the dev server has started, but when closed with Ctrl-C and restarted, fails.

Edit: With Yarn: Command failed with exit code 3221225477

** Environment **

Windows 10 (19043) x64
Node v16.13.2 x64 (and v14 also failed)
Launch via powershell in VS Code terminal (non-admin account, also tried with admin privileges)

Issue Analytics

State:
Created 2 years ago
Reactions:5
Comments:12 (3 by maintainers)

Top GitHub Comments

6reactions

devongovettcommented, Jan 27, 2022

I think we narrowed this down to an upgrade of napi-rs in the @parcel/source-map package, which was released sometime after Parcel 2.2.1. I still don’t know the exact root cause, but for now I’ve reverted this upgrade and published @parcel/source-map v2.0.2. See https://github.com/parcel-bundler/source-map/pull/91.

You’ll need to remove @parcel/source-map 2.0.1 from your lock file and re-install to get the upgrade. Please comment whether this works for you. Apologies again for the issue, and thanks for your patience while we track it down.

1reaction

devongovettcommented, Jan 26, 2022

Does it work for anyone if you set the PARCEL_WORKER_BACKEND=process environment variable?