After updating to parcel 2.2.1 the build system is flacky. It often fails. It take 2,3,4 runs to make it work.

🐛 bug report

After updating to parcel 2.2.1 the build system is flaky. It often fails. It takes 2,3,4 runs to make it work. /c/Program Files/nodejs/npm: line 44: 2128 Segmentation fault “$NODE_EXE” “$NPM_CLI_JS” “$@”

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

parcel watch src/web/pages/**/*.pug --dist-dir ./ --target public

{
  "plugins": [
    [
      "transform-react-pug",
      {
        "classAttribute": "className"
      }
    ],
    "styled-jsx/babel",
    "transform-jsx-css-modules",
    "@babel/plugin-transform-runtime"
  ]
}

🤔 Expected Behavior

It should work the first time.

😯 Current Behavior

After updating to parcel 2.2.1 the build system is flacky. It often fails. It take 2,3,4 runs to make it work. Sometimes it works aftet rimraffing .parcel_cache or npm rebuild, or both.

/c/Program Files/nodejs/npm: line 44: 2128 Segmentation fault “$NODE_EXE” “$NPM_CLI_JS” “$@”

💁 Possible Solution

Sometimes it works aftet rimraffing .parcel_cache or npm rebuild, or both.

🔦 Context

💻 Code Sample

🌍 Your Environment

Software	Version(s)
Parcel	2.2.1
Node	v16.13.2
npm/Yarn	npm 8.1.2
Operating System	Windows 10

[devongovett]

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.

[humphd]

I have 4 students hitting this bug tonight.