Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Npm install fails in npm-force-resolutions if there is a space in the user folder #17

Open
andremarcondesteixeira opened this issue Sep 21, 2020 · 5 comments
Open

Npm install fails in npm-force-resolutions if there is a space in the user folder #17

andremarcondesteixeira opened this issue Sep 21, 2020 · 5 comments

Comments

@andremarcondesteixeira
Copy link

Here is the error I am getting when running npm install:

Error: EPERM: operation not permitted, mkdir 'C:\Users\Andre'
command not found: npm-force-resolutions
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! cad-lite@0.1.0 preinstall: `npx npm-force-resolutions`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the cad-lite@0.1.0 preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Andre Teixeira\AppData\Roaming\npm-cache\_logs\2020-09-21T13_07_45_868Z-debug.log

Here is the debut log (C:\Users\Andre Teixeira\AppData\Roaming\npm-cache_logs\2020-09-21T13_07_45_868Z-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   'install'
1 verbose cli ]
2 info using npm@6.14.6
3 info using node@v12.18.3
4 verbose npm-session cdb3edcb11d401d1
5 silly install runPreinstallTopLevelLifecycles
6 silly preinstall cad-lite@0.1.0
7 info lifecycle cad-lite@0.1.0~preinstall: cad-lite@0.1.0
8 verbose lifecycle cad-lite@0.1.0~preinstall: unsafe-perm in lifecycle true
9 verbose lifecycle cad-lite@0.1.0~preinstall: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\projects\project_x\frontend\node_modules\.bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Symantec.cloud\PlatformAgent\;C:\Program Files\Git\cmd;C:\Program Files\nodejs\;C:\Program Files (x86)\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn\;C:\Program Files\Microsoft SQL Server\150\DTS\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;c:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;c:\Program Files\Microsoft SQL Server\110\Tools\Binn\;c:\Program Files\Microsoft SQL Server\110\DTS\Binn\;C:\Users\Andre Teixeira\AppData\Local\Microsoft\WindowsApps;C:\Users\Andre Teixeira\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Andre Teixeira\AppData\Roaming\npm;C:\Users\Andre Teixeira\.dotnet\tools
10 verbose lifecycle cad-lite@0.1.0~preinstall: CWD: C:\projects\project_x\frontend
11 silly lifecycle cad-lite@0.1.0~preinstall: Args: [ '/d /s /c', 'npx npm-force-resolutions' ]
12 silly lifecycle cad-lite@0.1.0~preinstall: Returned: code: 1  signal: null
13 info lifecycle cad-lite@0.1.0~preinstall: Failed to exec preinstall script
14 timing stage:rollbackFailedOptional Completed in 1ms
15 timing stage:runTopLevelLifecycles Completed in 1001ms
16 verbose stack Error: cad-lite@0.1.0 preinstall: `npx npm-force-resolutions`
16 verbose stack Exit status 1
16 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
16 verbose stack     at EventEmitter.emit (events.js:315:20)
16 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
16 verbose stack     at ChildProcess.emit (events.js:315:20)
16 verbose stack     at maybeClose (internal/child_process.js:1021:16)
16 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
17 verbose pkgid cad-lite@0.1.0
18 verbose cwd C:\projects\project_x\frontend
19 verbose Windows_NT 10.0.19041
20 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
21 verbose node v12.18.3
22 verbose npm  v6.14.6
23 error code ELIFECYCLE
24 error errno 1
25 error cad-lite@0.1.0 preinstall: `npx npm-force-resolutions`
25 error Exit status 1
26 error Failed at the cad-lite@0.1.0 preinstall script.
26 error This is probably not a problem with npm. There is likely additional logging output above.
27 verbose exit [ 1, true ]

I know it is not an npm preinstall error because if I try running any other command on preinstall, it works well.
@andremarcondesteixeira
Copy link
Author

A workaround is setting npm cache folder to another place:
npm config set cache C:\tmp\nodejs\npm-cache --global

@jamescarpinter jamescarpinter mentioned this issue Dec 18, 2020
Closed
@Eyegee-Eleven
Copy link

I am having this issue also...

@Eyegee-Eleven
Copy link

I am having this issue also...

I tried just about every suggestion I could find and then some. Running npm audit fix did the trick for me.

@kapilg007
Copy link

None of the above resolution worked for me. Any other fix for this?

@angelogiuseppe
Copy link

To anyone experiencing this issue, feel free to try: https://www.npmjs.com/package/force-resolutions

Just change:

"preinstall": "npx npm-force-resolutions"

To:

"preinstall": "npx force-resolutions"

npx force-resolutions does not run when no package-lock.json is detected, and allows the next command inline to be executed as normal. This is useful when installing dependencies for a package that has been already published where package-lock.json is not available.

If this issue persists please send more information to be able to replicate, and afterwards implement and adaptation

Feedback and PR's are welcome

beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 5, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
e6f4eda 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 5, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
160fbb4 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 5, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
752beb9 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 5, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
dffcda1 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 5, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
65d5b59 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 5, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
775e55c 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 5, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
9ba6d8a 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 5, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
9991b8d 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 6, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
5fe8b4b 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 6, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
ff660cd 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 6, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
9423e32 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 6, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
55d4c92 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 6, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
25163e5 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 6, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
2e8d9b2 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 6, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
e1266d6 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 6, 2022
@beatrizsmerino
fix(ci): wrong ‘node' and ‘deploy' workflows
eb29c78 
Error:
- In the `node` workflow, the `npm ci` command needs the `package-lock.json` file to work, but this file is removed before running `npm install` with the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Update the `preinstall` npm script to make it faster.
- In the `node` workflow, use the `npm install` command instead of `npm ci`, this command auto runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 6, 2022
@beatrizsmerino
fix(ci): wrong 'node' and 'deploy' workflows when using node versions…
c17267b 
… >14

Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` file is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.
- Use `node` version 14 for the project, the following versions still do not work.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 6, 2022
@beatrizsmerino
fix(ci): wrong 'node' and 'deploy' workflows when using node versions…
2fa5058 
… >14

Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` file is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.
- Use `node` version 14 for the project, the following versions still do not work.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 6, 2022
@beatrizsmerino
fix(ci): wrong 'node' and 'deploy' workflows when using node versions…
b70513e 
… >14

Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` file is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.
- Use `node` version 14 for the project, the following versions still do not work.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-editor that referenced this issue Jul 6, 2022
@beatrizsmerino
fix(ci): wrong 'node' and 'deploy' workflows when using node versions…
cecba97 
… >14

Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.
- In the `node` workflow, the version 16 check does not work because the `console.log` file is not allowed by eslint in the `EditorJson.vue` file.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Disables the `no-console` slint rule in the `EditorJson.vue` file.
- Use `node` version 14 for the project, the following versions still do not work.

Resolutions:
- https://stackoverflow.com/a/68095189/10855837
- https://stackoverflow.com/a/53325242/10855837
- rogeriochaves/npm-force-resolutions#17
- https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-todolist that referenced this issue Jul 6, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
f4dee39 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-todolist that referenced this issue Jul 6, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
ed050dc 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-todolist that referenced this issue Jul 6, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
8a75a8b 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-todolist that referenced this issue Jul 6, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
22feba7 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-todolist that referenced this issue Jul 6, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
54cdc6c 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/calendar that referenced this issue Jul 7, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
00693e9 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/calendar that referenced this issue Jul 7, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
632f4c7 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/calendar that referenced this issue Jul 7, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
776bcc7 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-todolist that referenced this issue Jul 7, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
2a20c57 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/validation-form that referenced this issue Jul 7, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
d97749b 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/git-bible that referenced this issue Jul 7, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
5a8716e 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-gh-pages that referenced this issue Jul 7, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
d0ba9b3 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-users that referenced this issue Jul 7, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
9a48fba 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/gulp-compiler that referenced this issue Jul 7, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
1721798 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/nuxt-course that referenced this issue Jul 7, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
c1aba35 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/calendar that referenced this issue Nov 10, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
1f6a2bd 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/gulp-compiler that referenced this issue Nov 10, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
32a98f2 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/validation-form that referenced this issue Nov 10, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
0f2add7 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-users that referenced this issue Nov 10, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
6e5003f 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
beatrizsmerino added a commit to beatrizsmerino/vue-gh-pages that referenced this issue Nov 10, 2022
@beatrizsmerino
BUGFIX. Wrong 'node' and 'deploy' workflows when using node versions >14
d19b844 
Error:
- In the `node` workflow, the `npm ci` command does not work, it needs the `package-lock.json` file to work, but this file is removed by the npm `preinstall` script.

Solution:
- Use in workflows the `npm install` command instead of `npm ci`. The `npm install` automatically runs the npm `preinstall` script which already does a clean install, removing the `node_modules` folder and the `package-lock.json` file.
- Use `node` version 14 for the project, the following versions still do not work.

References:
- npm-force-resolutions not working when installing a new package
https://stackoverflow.com/a/68095189/10855837
- What is the difference between "npm install" and "npm ci"?
https://stackoverflow.com/a/53325242/10855837
- Npm install fails in npm-force-resolutions if there is a space in the user folder
rogeriochaves/npm-force-resolutions#17
- NPM force-resolutions
https://www.npmjs.com/package/force-resolutions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@andremarcondesteixeira @angelogiuseppe @kapilg007 @Eyegee-Eleven