包裹错误 - 找不到模块@parcel\\fs-search\\fs-search.win32-x64-msvc.node

Question

I recently updated my windows from windows 10 to 11.我最近将我的 Windows 从 Windows 10 更新到了 11。

** Update ** I've reinstalled windows 10 again, but I'm receiving the same error ** 更新 ** 我再次重新安装了 Windows 10，但我收到了同样的错误

When I rund yarn start, or npm start, I receive the below error当我运行 yarn start 或 npm start 时，我收到以下错误

λ 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.

my setup is very simple, here're the details我的设置很简单，这里是详细信息

package.json file package.json 文件

{
  "name": "testing",
  "version": "1.0.0",
  "license": "MIT",
  "scripts": {
    "start": "parcel index.html",
    "build": "parcel build"
  },
  "devDependencies": {
    "parcel": "^2.0.0"
  }
}

nothing special in my index.html or my javascript file,我的 index.html 或我的 javascript 文件中没有什么特别的，

html file html文件

<!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>

javascript file javascript文件

console.log("Hello world");

my Environment我的环境

Parcel  2
Node    v14.18.1
npm/Yarn    
Operating System    Windows 11 Pro
Version 21H2
OS build 22000.258
experience Windows Feature Experience Pack 1000.22000.258.0

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奇怪的是，当我查看错误中的指定文件夹时，发现模块 "fs-search.win32-x64-msvc.node" ，它已经在以下目录下

node_moduels/@parcel/fs-search /fs-search.win32-x64-msvc.node node_moduels/@parcel/fs-search /fs-search.win32-x64-msvc.node

It's already exist, however the error claiming it's not found!它已经存在，但是错误声称找不到它！ 😕 😕

I've removed node_modules, several times and reinstalled parcel again, however the same error accrud, I'm not sure what could be causing this issue, any one can help?我已经多次删除 node_modules 并再次重新安装了parcel，但是产生了相同的错误，我不确定是什么导致了这个问题，有人可以帮忙吗？

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 npm@6.14.15
3 info using node@v14.18.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle testing@1.0.0~prestart: testing@1.0.0
6 info lifecycle testing@1.0.0~start: testing@1.0.0
7 verbose lifecycle testing@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle testing@1.0.0~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 testing@1.0.0~start: CWD: C:\Users\Ammar Home\Desktop\testing
10 silly lifecycle testing@1.0.0~start: Args: [ '/d /s /c', 'parcel index.html' ]
11 silly lifecycle testing@1.0.0~start: Returned: code: 1  signal: null
12 info lifecycle testing@1.0.0~start: Failed to exec start script
13 verbose stack Error: testing@1.0.0 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 testing@1.0.0
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 testing@1.0.0 start: `parcel index.html`
22 error Exit status 1
23 error Failed at the testing@1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Answer 1

I can't reproduce this on my end with the same node and win10 versions.我无法使用相同的节点和 win10 版本在我的一端重现此问题。 However, according to this answer (about an unreladed package) the "module could not be found" error can occur when the native module file (which does exist) tries to load a dependency that's not present on the system.但是，根据此答案（关于未关联的包），当本机模块文件（确实存在）尝试加载系统上不存在的依赖项时，可能会发生“找不到模块”错误。 You could try using Dependency Walker to check the dependencies of node_moduels/@parcel/fs-search/fs-search.win32-x64-msvc.node on your machine and see if they are all installed.您可以尝试使用Dependency Walker检查您机器上的node_moduels/@parcel/fs-search/fs-search.win32-x64-msvc.node的依赖项，看看它们是否都已安装。

Answer 2

The issue caused due to missing library on the computer.由于计算机上缺少库而导致的问题。 fs-search requires Microsoft Visual C++ 2015 Redistributable (x64). fs-search 需要 Microsoft Visual C++ 2015 Redistributable (x64)。

You can get the download here -> https://aka.ms/vs/17/release/vc_redist.x64.exe你可以在这里下载 -> https://aka.ms/vs/17/release/vc_redist.x64.exe

I've got the answer from github issues on parcel我从关于parcel的github问题得到了答案

https://github.com/parcel-bundler/parcel/issues/7104 https://github.com/parcel-bundler/parcel/issues/7104

Thank you,谢谢，

包裹错误 - 找不到模块@parcel\\fs-search\\fs-search.win32-x64-msvc.node

问题描述

2 个解决方案

解决方案1
0 2021-10-19 21:14:00

解决方案2
0 已采纳 2021-11-13 23:59:53

包裹错误 - 找不到模块@parcel\\fs-search\\fs-search.win32-x64-msvc.node

问题描述

2 个解决方案

解决方案1 0 2021-10-19 21:14:00

解决方案2 0 已采纳 2021-11-13 23:59:53

解决方案1
0 2021-10-19 21:14:00

解决方案2
0 已采纳 2021-11-13 23:59:53