Ctrl-c exit on windows hangs

🐛 bug report

When using Ctrl-C I get the “Parcel is shutting down” message and then it just hangs.
Running from .bin or npm/npx all same problem. If i terminate the script with repeated Ctrl-C commands, the node process is still running and I then have to kill it manually This happens even when the only thing I am compiling is a barebones HTML file

Presumably something with my setup? as no one else has raised this, but I’m not aware of any other issues with node, and wondering if other may also have the same problem.

🤔 Expected Behavior

It should exit to the terminal prompt

😯 Current Behavior

It just hangs on “shutting down” message

🌍 Your Environment

Software	Version(s)
Parcel	2.0.0-nightly.452
Node	12.0.0
npm/Yarn	6.9.0
Operating System	Windows 10

🎛 Configuration (.babelrc, package.json, cli command)

calling npx parcel serve …/index.html

no babel config,

{
  "name": "soap-app-sample",
  "version": "1.0.0",
  "dependencies": {
    "@azure/service-bus": "^7.0.0-preview.8",
    "@soap/modules": "^1.17.0",
    "@soap/react": "^1.11.0",
    "prop-types": "15.7.2",
    "react": "^16.14.0",
    "react-dom": "^16.14.0",
    "sanitize.css": "^8.0.1"
  },
  "devDependencies": {
    "parcel": "^2.0.0-beta.1",
    "@babel/core": "7.4.3"
  },
  "scripts": {
    "build": "npx parcel build ../index.html --public-url ./",
    "run": "npx parcel serve ../index.html"
  }
}

[lucasdavidferrero]

Not sure how this is related, but there seems to be some relation to #7271 (when a lock file exists higher up in the file tree, it fails).

I was also experiencing this issue (Node 16, npm 8, Windows 10, Parcel 2.3.2), and after deleting a package-lock.json file, I found higher up in the file tree (3 levels up, in my case), it solved this issue for me, as well.

So I’m not sure if/how this is related, but my best guess is that a lock file higher up the package tree brings Parcel into some undefined state where all kinds of weird stuff can happen 🤔 .

Not sure if this is “the only issue” at play, here, but maybe it’ll help somebody 🙂

I can confirm that I’m facing both: this issue and #7271. Node 16, Parcel 2.3.2, yarn 3.2.0 on Windows 10.

So, there must be some kind of relation as @pklaschka says.

[pklaschka]

Not sure how this is related, but there seems to be some relation to #7271 (when a lock file exists higher up in the file tree, it fails).

I was also experiencing this issue (Node 16, npm 8, Windows 10, Parcel 2.3.2), and after deleting a package-lock.json file, I found higher up in the file tree (3 levels up, in my case), it solved this issue for me, as well.

So I’m not sure if/how this is related, but my best guess is that a lock file higher up the package tree brings Parcel into some undefined state where all kinds of weird stuff can happen 🤔 .

Not sure if this is “the only issue” at play, here, but maybe it’ll help somebody 🙂