@parcel/transformer-css: Could not resolve module ...\@parcel\css\parcel-css.win32-x64-msvc.node

[Tomalak]

🐛 bug report

Parcel 2.6.0 build fails on Windows as soon as CSS needs to be compiled.

EDIT: I've tried some more, and this works as expected in yarn 1 (1.22.19). It starts failing with yarn 2+.

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

Minimal reproducible example:

package.json

{
  "name": "test",
  "packageManager": "yarn@3.2.1",
  "devDependencies": {
    "parcel": "^2.6.0"
  }
}

index.html (style.css can be empty)

<link rel="stylesheet" href="style.css">

CLI command

yarn parcel index.html --open

🤔 Expected Behavior

It should compile and show the website.

😯 Current Behavior

Server running at http://localhost:1234
× Build failed.

@parcel/transformer-css: Could not resolve module "D:\wwwroot\test\.yarn\cache\@parcel-css-npm-1.10.0-0cacf3a9ad-041eab1128.zip\node_modules\@parcel\css\parcel-css.win32-x64-msvc.node" from
"D:\wwwroot\test\.yarn\cache\@parcel-css-npm-1.10.0-0cacf3a9ad-041eab1128.zip\node_modules\@parcel\css\node\index.js"

  Error: Could not resolve module "D:\wwwroot\test\.yarn\cache\@parcel-css-npm-1.10.0-0cacf3a9ad-041eab1128.zip\node_modules\@parcel\css\parcel-css.win32-x64-msvc.node" from
  "D:\wwwroot\test\.yarn\cache\@parcel-css-npm-1.10.0-0cacf3a9ad-041eab1128.zip\node_modules\@parcel\css\node\index.js"
      at $0578d0f6e116167e$export$fb2a0b866a8162dc.resolve
  (D:\wwwroot\test\.yarn\__virtual__\@parcel-package-manager-virtual-712660d03a\0\cache\@parcel-package-manager-npm-2.6.0-a1bc9cb3f8-57da82e799.zip\node_modules\@parcel\package-manager\lib\index.js:5000:21)
      at NodePackageManager.resolveSync
  (D:\wwwroot\test\.yarn\__virtual__\@parcel-package-manager-virtual-712660d03a\0\cache\@parcel-package-manager-npm-2.6.0-a1bc9cb3f8-57da82e799.zip\node_modules\@parcel\package-manager\lib\index.js:3508:42)
      at NodePackageManager.requireSync
  (D:\wwwroot\test\.yarn\__virtual__\@parcel-package-manager-virtual-712660d03a\0\cache\@parcel-package-manager-npm-2.6.0-a1bc9cb3f8-57da82e799.zip\node_modules\@parcel\package-manager\lib\index.js:3351:34)
      at Module.m.require (D:\wwwroot\test\.yarn\__virtual__\@parcel-package-manager-virtual-712660d03a\0\cache\@parcel-package-manager-npm-2.6.0-a1bc9cb3f8-57da82e799.zip\node_modules\@parcel\package-manager\lib\index.js:3365:25)
      at require (node:internal/modules/cjs/helpers:102:18)
      at Object.<anonymous> (D:\wwwroot\test\.yarn\cache\@parcel-css-npm-1.10.0-0cacf3a9ad-041eab1128.zip\node_modules\@parcel\css\node\index.js:21:22)
      at Module._compile (node:internal/modules/cjs/loader:1105:14)
      at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
      at Object.require$$0.Module._extensions..js (D:\wwwroot\test\.pnp.cjs:11669:33)
      at Object.require$$0.Module._extensions..js (D:\wwwroot\test\.pnp.cjs:11669:33)

Removing the <style> tag from index.html removes the error, so parcel works in principle, the issue is limited to plugins.

🔦 Context

This is a bare-bones example, just enough to trigger the error. There is not a lot of context besides what's shown.

💻 Code Sample

Everything there is is shown above.

🌍 My Environment

Software	Version(s)
Parcel	2.6.0
Node	16.15.1 64 bit (via nvm for Windows 1.9.0)
npm	8.12.1
Yarn	3.2.1 (via corepack + yarn set version stable)
Operating System	Windows 10 21H2 (19044.1741)

[mischnic]

What happens if you run require("@parcel/css-win32-x64-msvc") in that project? (Using yarn node to get a REPL)

[Tomalak]

@mischnic

D:\wwwroot\test>yarn node
Welcome to Node.js v16.15.1.
Type ".help" for more information.
> require("@parcel/css-win32-x64-msvc")
Uncaught:
Error: Your application tried to access @parcel/css-win32-x64-msvc, but it isn't declared in your dependencies; this makes the require call ambiguous and unsound.

Required package: @parcel/css-win32-x64-msvc (via "@parcel\css-win32-x64-msvc")
Required by: D:\wwwroot\test\

Require stack:
- <repl>
    at Function.require$$0.Module._resolveFilename (D:\wwwroot\test\.pnp.cjs:11625:13)
    at Function.require$$0.Module._load (D:\wwwroot\test\.pnp.cjs:11479:42)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
>

[mischnic]

Ah, forgot about that. Is the parcel-css Windows package listed in .yarn/unplugged? this is what I get with your package.json on macOS

$ ls .yarn/unplugged/
.                                                                  @parcel-watcher-npm-2.0.5-bda35fb0f8
..                                                                 lmdb-darwin-x64-npm-2.3.10-5d8ffc96fc
@msgpackr-extract-msgpackr-extract-darwin-x64-npm-2.0.2-aaad2bbcdd lmdb-npm-2.3.10-c5ad6989ec
@parcel-css-darwin-x64-npm-1.10.0-a2732c7c5c                       msgpackr-extract-npm-2.0.2-27402474ca
@parcel-fs-search-npm-2.6.0-5acc4c8e21                             nan-npm-2.16.0-cac314a230
@parcel-hash-npm-2.6.0-b6dad0d549                                  node-addon-api-npm-3.2.1-a29528f81d
@parcel-optimizer-image-npm-2.6.0-64f4328571                       node-addon-api-npm-4.3.0-a07a1232df
@parcel-source-map-npm-2.0.5-2444d2c092                            node-gyp-npm-9.0.0-0eccfca4d1
@parcel-transformer-js-virtual-de973eb34b                          term-size-npm-2.2.1-77ce7141d0

[Tomalak]

@mischnic Nope. (But there is a @parcel-css-npm-1-10.0-*.zip in .yarn\cache.)

D:\wwwroot\test>dir /b .yarn\unplugged
@msgpackr-extract-msgpackr-extract-win32-x64-npm-2.0.2-c54981be26
@parcel-fs-search-npm-2.6.0-5acc4c8e21
@parcel-hash-npm-2.6.0-b6dad0d549
@parcel-optimizer-image-npm-2.6.0-64f4328571
@parcel-source-map-npm-2.0.5-2444d2c092
@parcel-transformer-js-virtual-de973eb34b
@parcel-watcher-npm-2.0.5-bda35fb0f8
lmdb-npm-2.3.10-c5ad6989ec
lmdb-win32-x64-npm-2.3.10-2fbb194830
msgpackr-extract-npm-2.0.2-27402474ca
nan-npm-2.16.0-cac314a230
node-addon-api-npm-3.2.1-a29528f81d
node-addon-api-npm-4.3.0-a07a1232df
node-gyp-npm-9.0.0-0eccfca4d1
term-size-npm-2.2.1-77ce7141d0

Yarn itself finishes with a bunch of warnings, not sure if that's the expected behavior.

(click to view yarn output)

D:\wwwroot\test>yarn
➤ YN0000: ┌ Resolution step
➤ YN0032: │ @parcel/watcher@npm:2.0.5: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ msgpackr-extract@npm:2.0.2: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ node-addon-api@npm:3.2.1: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ lmdb@npm:2.3.10: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ node-addon-api@npm:4.3.0: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ nan@npm:2.16.0: Implicit dependencies on node-gyp are discouraged
➤ YN0002: │ @parcel/optimizer-image@npm:2.6.0 doesn't provide @parcel/core (pf3b9c), requested by @parcel/workers
➤ YN0002: │ @parcel/types@npm:2.6.0 doesn't provide @parcel/core (p4cfd8), requested by @parcel/fs
➤ YN0002: │ @parcel/types@npm:2.6.0 doesn't provide @parcel/core (pe8e32), requested by @parcel/workers
➤ YN0002: │ @parcel/types@npm:2.6.0 doesn't provide @parcel/core (p1d308), requested by @parcel/cache
➤ YN0002: │ @parcel/types@npm:2.6.0 doesn't provide @parcel/core (p33c58), requested by @parcel/package-manager
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 5s 648ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ wide-align@npm:1.1.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrappy@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xxhash-wasm@npm:0.4.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yaml@npm:1.10.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0000: └ Completed in 0s 824ms
➤ YN0000: ┌ Link step
➤ YN0000: │ ESM support for PnP uses the experimental loader API and is therefore experimental
➤ YN0007: │ lmdb@npm:2.3.10 must be built because it never has been before or the last one failed
➤ YN0007: │ msgpackr-extract@npm:2.0.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @parcel/watcher@npm:2.0.5 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 3s 260ms
➤ YN0000: Done with warnings in 9s 774ms

[merceyz]

This is happening because the libc field is set to msvc which doesn't match the current version of null so its skipped.
The libc field should be removed from the win32 package but in the meantime you can workaround it by explicitly requesting the msvc version using supportedArchitectures.

supportedArchitectures:
  libc: [msvc, current]

[nirtutac123]

PS C:\Users\Dell\Desktop\namaste-react> npx parcel index.html
Server running at http://localhost:1234
🚨 Build failed.

Error: Could not resolve module "@parcel/transformer-js-win32-x64-msvc"
from
"C:\Users\Dell\Desktop\namaste-react\node_modules@parcel\transformer-js\native.js"

Error: Could not resolve module "@parcel/transformer-js-win32-x64-msvc"
from
"C:\Users\Dell\Desktop\namaste-react\node_modules@parcel\transformer-js\native.js"
at NodePackageManager.resolveInternal
(C:\Users\Dell\Desktop\namaste-react\node_modules@parcel\package-manager\lib\index.js:3672:21)
at NodePackageManager.resolveSync
(C:\Users\Dell\Desktop\namaste-react\node_modules@parcel\package-manager\lib\index.js:3567:29)
at NodePackageManager.requireSync
(C:\Users\Dell\Desktop\namaste-react\node_modules@parcel\package-manager\lib\index.js:3394:34)
at m.require
(C:\Users\Dell\Desktop\namaste-react\node_modules@parcel\package-manager\lib\index.js:3410:25)
at require (node:internal/modules/cjs/helpers:103:18)
at Object.
(C:\Users\Dell\Desktop\namaste-react\node_modules@parcel\transformer-js\native.js:72:29)