Description
🐛 bug report
Parcel gives me an error when I run yarn start, or yarn build, or npm start or build
I recently upgraded to windows 11
** Updates: **
I've rolled back to a fresh installation of windows 10, and I got the same error 😒, I'm not sure what's happening here but it seems like there's some mistake in parcel installation.
🎛 Configuration ( package.json)
{
"name": "testing",
"version": "1.0.0",
"license": "MIT",
"scripts": {
"start": "parcel index.html",
"build": "parcel build"
},
"devDependencies": {
"parcel": "^2.0.0"
}
}
🤔 Expected Behavior
It should run the build or the development server, but neither happened
😯 Current Behavior
An error in the terminal
λ yarn start
yarn run v1.22.15
$ parcel index.html
Error: The specified module could not be found.
\\?\C:\Users\Ammar Home\Desktop\testing\node_modules\@parcel\fs-search\fs-search.win32-x64-msvc.node
at Object.Module._extensions..node (internal/modules/cjs/loader.js:1144:18)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (C:\Users\Ammar Home\Desktop\testing\node_modules\v8-compile-cache\v8-compile-cache.js:159:20)
at Object.<anonymous> (C:\Users\Ammar Home\Desktop\testing\node_modules\@parcel\fs-search\index.js:19:20)
at Module._compile (C:\Users\Ammar Home\Desktop\testing\node_modules\v8-compile-cache\v8-compile-cache.js:192:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12) {
code: 'ERR_DLOPEN_FAILED'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
💁 Possible Solution
I removed entire node module , reinstalled parcel several times, and still facing the same issue
🔦 Context
Just runing a normal start script to see a console log in the browser, it was just a startup file
💻 Code Sample
I have nothing special in my code, it's just a startup file
index.html file
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Document</title>
</head>
<body>
<script src="./index.js" type="module"></script>
</body>
</html>
index.js file
console.log("Hello world");
🌍 Environment
Software | Version(s) |
---|---|
Parcel | "^2.0.0" |
Node | v14.18.1 |
npm | 6.14.15 |
Yarn | 1.22.15 |
Operating System | Windows 11 Pro |
Version | 21H2 |
OS build | 22000.258 |
Experience | Windows Feature Experience Pack 1000.22000.258.0 |
My labtop specification
Processor | Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz 1.80 GHz |
Installed RAM | 8.00 GB (7.88 GB usable) |
System type | 64-bit operating system, x64-based processor |
The wierd thing is when I looked at the specified folder in the error, I found that module "fs-search.win32-x64-msvc.node" , It's already there under following directory
- node_moduels /
-- @parcel /
---fs-search /
---- fs-search.win32-x64-msvc.node
, which the error claiming it's not found! 😕
I'm not sure what could be causing this issue,
any one can help?
Debug log:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\Ammar Home\Desktop\testing\node_modules\.bin;C:\Users\Ammar Home\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\Users\Ammar Home\cmder\vendor\conemu-maximus5;C:\Users\Ammar Home\cmder\vendor\conemu-maximus5\ConEmu;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\Program Files\nodejs\;C:\Users\Ammar Home\AppData\Local\Microsoft\WindowsApps;C:\Users\Ammar Home\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Ammar Home\AppData\Roaming\npm;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\Ammar Home\cmder\vendor\bin;C:\Users\Ammar Home\cmder
9 verbose lifecycle [email protected]~start: CWD: C:\Users\Ammar Home\Desktop\testing
10 silly lifecycle [email protected]~start: Args: [ '/d /s /c', 'parcel index.html' ]
11 silly lifecycle [email protected]~start: Returned: code: 1 signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: `parcel index.html`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:400:28)
13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:400:28)
13 verbose stack at maybeClose (internal/child_process.js:1058:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
14 verbose pkgid [email protected]
15 verbose cwd C:\Users\Ammar Home\Desktop\testing
16 verbose Windows_NT 10.0.22000
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v14.18.1
19 verbose npm v6.14.15
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: `parcel index.html`
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]