提问人:Rodrigo 提问时间:9/17/2021 最后编辑:RobCRodrigo 更新时间:4/29/2022 访问量:15979
无法从 watchpack-chokidar2:fsevents 访问 NPM CI 错误绑定
NPM CI error bindings not accessible from watchpack-chokidar2:fsevents
问:
当我在 Github Actions 上运行时,出现错误:npm ci
Run npm ci
npm ERR! bindings not accessible from watchpack-chokidar2:fsevents
npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2021-09-17T15_18_42_465Z-debug.log
Error: Process completed with exit code 1.
可能是什么?
我.github/workflows/eslint.yaml
name: ESLint
on: [push, pull_request]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Use Node.js
uses: actions/setup-node@v1
with:
node-version: '14.x'
- run: npm ci
- run: npm run lint
我package.json
{
"name": "@blinktrade/uikit",
"version": "1.0.0",
"main": "dist/index.js",
"license": "MIT",
"devDependencies": {
"@babel/plugin-transform-react-jsx": "^7.14.9",
"@babel/preset-env": "^7.15.6",
"@babel/preset-react": "^7.14.5",
"@babel/preset-typescript": "^7.15.0",
"@storybook/addon-essentials": "^6.3.8",
"@storybook/react": "^6.3.8",
"@testing-library/jest-dom": "^5.14.1",
"@testing-library/react": "^12.1.0",
"@testing-library/user-event": "^13.2.1",
"@types/jest": "^27.0.1",
"@types/react": "^17.0.21",
"@typescript-eslint/eslint-plugin": "^4.31.1",
"@typescript-eslint/parser": "^4.31.1",
"eslint": "^7.32.0",
"eslint-plugin-react": "^7.25.2",
"husky": "^7.0.2",
"jest": "^27.2.0",
"prettier": "^2.4.1",
"pretty-quick": "^3.1.1",
"react": "^17.0.2",
"react-dom": "^17.0.2",
"rimraf": "^3.0.2",
"typescript": "^4.4.3"
},
"husky": {
"hooks": {
"pre-push": "npm run lint",
"pre-commit": "pretty-quick --staged"
}
},
"scripts": {
"build": "tsc -p .",
"clear": "rimraf dist/",
"format": "prettier '**/*' --write --ignore-unknown",
"lint": "eslint --max-warnings=0 .",
"storybook": "start-storybook -p 4000",
"test": "jest"
}
}
答:
10赞
Rodrigo
9/21/2021
#1
解决了删除packages-lock.json并使用 NodeJS 14(原为 10)再次运行的问题
评论
0赞
NiroshanJ
11/16/2023
就我而言,当我使用.nvmrc文件中指定的节点版本时,它工作正常
0赞
Ryabchenko Alexander
10/24/2021
#2
为我帮助更新了节点版本
3赞
Exiled
2/2/2022
#3
在 GitHub 操作和已构建的本地环境中必须具有相同的版本。就我而言,GitHub 操作指向 .actions/setup-node@v1
package-lock.json
node 14
- uses: actions/setup-node@v1
with:
node-version: "14"
将其更改为(与我在本地环境中相同的)后,它解决了问题。16
1赞
Hashim Aziz
4/29/2022
#4
就我而言,尽管已经工作了一段时间并且与我的本地 Node 版本匹配,但我的测试突然开始失败,奇怪的是。只需在我的 GitHub Action 工作流程中将其更新为 16 即可解决该问题并导致测试再次开始运行:node_version
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: 16
0赞
Anzor
4/29/2022
#5
在构建映像设置中,我添加了“Node.js 版本 16.15”包。它帮助了我!
评论