800A03EA javascript语法JScript编译错误
800A03EA javascript语法JScript编译错误
提问于 2020-05-23 05:17:36
一个非常恼人的编译问题正在发生在我的计算机上关于JScript和节点，我已经尝试了几条由互联网提供的指令，但是这个问题似乎仍然存在。
CD>PROJECT
npm init好的
npm install -g和本地ok
npm start >start问题:脚本> app.js或node app.js确定
如果它运行，我会收到Windows主机服务器错误#800A03EA语法/编译问题。
但是，如果我运行代码npx http-server，我可以在没有问题的情况下完成PWA项目。
我已经尝试过几个“修复”工具，修复，注册表验证，但他们似乎没有解决问题。
回答 3
Stack Overflow用户
回答已采纳
发布于 2020-05-23 08:27:02
JScript (由windows脚本主机解释)与JavaScript不一样(由节点*解释)。
上面提到的错误听起来似乎是Windows主机的JScript解释器试图执行一个用于节点的JavaScript文件。
确保您使用节点(node app.js)运行代码，而不是使用WSH。*.JS窗口中的默认文件关联是WSH，所以双倍或只运行app.js就会运行WSH。
另外，确保start命令在package.json中实际上被设置为node app.js，我觉得它只被设置为app.js。
...
"scripts": {
"start": "node app.js"
}
... 那么，npm start应该可以工作。
*：当然，节点不是Javascript的唯一解释器，但它是与此相关的。
Stack Overflow用户
发布于 2020-05-23 18:48:45
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:\\Users\\Dev\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm@6.14.5
3 info using node@v12.16.3
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle np@1.0.0~prestart: np@1.0.0
6 info lifecycle np@1.0.0~start: np@1.0.0
7 verbose lifecycle np@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle np@1.0.0~start: PATH: C:\Users\Dev\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\Dev\Desktop\Fetch api\node_modules\.bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Python38\Scripts\;C:\Python38\;C:\Program Files (x86)\Intel\TXE Components\iCLS\;C:\Program Files\Intel\TXE Components\iCLS\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files\Intel\TXE Components\DAL\;C:\Program Files (x86)\Intel\TXE Components\DAL\;C:\Program Files\Intel\TXE Components\IPT\;C:\Program Files (x86)\Intel\TXE Components\IPT\;C:\ProgramData\chocolatey\bin;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files\dotnet\;C:\Program Files (x86)\dotnet\;C:\Users\Dev\AppData\Local\Microsoft\WindowsApps;;C:\Users\Dev\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Dev\AppData\Roaming\npm
9 verbose lifecycle np@1.0.0~start: CWD: C:\Users\Dev\Desktop\Fetch api
10 silly lifecycle np@1.0.0~start: Args: [ '/d /s /c', 'node scripts.js' ]
11 silly lifecycle np@1.0.0~start: Returned: code: 1 signal: null
12 info lifecycle np@1.0.0~start: Failed to exec start script
13 verbose stack Error: np@1.0.0 start: `node scripts.js`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\Dev\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:310:20)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\Dev\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:310:20)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid np@1.0.0
15 verbose cwd C:\Users\Dev\Desktop\Fetch api
16 verbose Windows_NT 10.0.17763
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Dev\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v12.16.3
19 verbose npm v6.14.5
20 error code ELIFECYCLE
21 error errno 1
22 error np@1.0.0 start: `node scripts.js`
22 error Exit status 1
23 error Failed at the np@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 ]
PS C:\Users\Dev\Desktop\Fetch api> npm start
> np@1.0.0 start C:\Users\Dev\Desktop\Fetch api
> node scripts.js
C:\Users\Dev\Desktop\Fetch api\scripts.js:1
var button = document.querySelector('.button')
^
ReferenceError: document is not defined
at Object.<anonymous> (C:\Users\Dev\Desktop\Fetch api\scripts.js:1:14)
at Module._compile (internal/modules/cjs/loader.js:1133:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
at Module.load (internal/modules/cjs/loader.js:977:32)
at Function.Module._load (internal/modules/cjs/loader.js:877:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12)
at internal/main/run_main_module.js:18:47
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! np@1.0.0 start: `node scripts.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the np@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Dev\AppData\Roaming\npm-cache\_logs\2020-05-23T18_39_34_693Z-debug.log
PACKAGE JSON
{
"name": "np",
"version": "1.0.0",
"main": "script.js",
"scripts": {
"start": "node scripts.js",
"test": "echo \"Error: no test specified\" && exit 1"
},
"author": "",
"license": "ISC",
"dependencies": {
"npm": "^6.14.5",
"prpl-server": "^1.4.0"
},
"devDependencies": {},
"repository": {
"type": "git",
"url": "https://github.com/mendesbayout/Fetch-api-simple-forecast.git"
},
"bugs": {
"url": "https://github.com/mendesbayout/Fetch-api-simple-forecast/issues"
},
"homepage": "https://github.com/mendesbayout/Fetch-api-simple-forecast#readme",
"description": ""
}
Stack Overflow用户
发布于 2022-05-30 11:31:59
在js文件的开头添加这一行：
#!/usr/bin/env node它将告诉您的系统使用哪个解释器来运行文件。
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/61967777
复制相关文章
相似问题
腾讯云开发者
