【发布时间】:2020-11-09 13:03:54
【问题描述】:
据我了解,“perf_hooks”是 Node.js 的一部分。但是,当使用npm test 进行测试时,我会失败并出现以下情况(某些文件名已更改):
Error: ENOENT: no such file or directory, open 'perf_hooks'
at Object.openSync (fs.js:465:3)
at Object.readFileSync (fs.js:368:35)
at SandboxedModule._getCompileInfo (node_modules/sandboxed-module/lib/sandboxed_module.js:265:20)
at SandboxedModule._compile (node_modules/sandboxed-module/lib/sandboxed_module.js:245:22)
at createInnerSandboxedModule (node_modules/sandboxed-module/lib/sandboxed_module.js:183:23)
at SandboxedModule.RecursiveRequireProxy (node_modules/sandboxed-module/lib/sandboxed_module.js:214:27)
at /Users/asmirnov/Documents/blabla2.js:51:12
at Object.<anonymous> (lib/profiler.js:53:3)
at SandboxedModule._compile (node_modules/sandboxed-module/lib/sandboxed_module.js:251:19)
at createInnerSandboxedModule (node_modules/sandboxed-module/lib/sandboxed_module.js:183:23)
at SandboxedModule.RecursiveRequireProxy (node_modules/sandboxed-module/lib/sandboxed_module.js:214:27)
at Object.<anonymous> (lib/blabla1.js:29:20)
at SandboxedModule._compile (node_modules/sandboxed-module/lib/sandboxed_module.js:251:19)
at createInnerSandboxedModule (node_modules/sandboxed-module/lib/sandboxed_module.js:183:23)
at SandboxedModule.RecursiveRequireProxy (node_modules/sandboxed-module/lib/sandboxed_module.js:214:27)
at SandboxedModule.requireInterceptor (node_modules/sandboxed-module/lib/sandboxed_module.js:227:9)
at Context.<anonymous> (test/blabla1.js:73:22)
at processImmediate (internal/timers.js:458:21)
这是使用它的文件 (lib/profiler.js) 的一部分:
const {performance, PerformanceObserver} = (function()
{
try
{
if (window && typeof window.performance == "undefined")
throw new TypeError();
return window;
}
catch (e)
{
return require("perf_hooks");
}
})();
可能是什么原因?但是在某些情况下(npm run ..),它会按预期工作。任何建议表示赞赏。
PS。节点比较新鲜:
> node --version
v14.8.0
【问题讨论】:
-
这很奇怪,the documentation 说它应该位于
lib/perf_hooks.js但在我的安装中这个文件也丢失了 -
perf_hooks确实在那个版本的 Node.js 中。在 14.8.0 中,require()在找不到模块时会抛出MODULE_NOT_FOUND(而不是ENOENT),因此问题出在其他问题上。
标签: javascript npm chromium benchmarking