Skip to content

getting errors on npm install #500

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.

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

Closed
KraToS-zz opened this issue Feb 1, 2020 · 12 comments
Closed

getting errors on npm install #500

KraToS-zz opened this issue Feb 1, 2020 · 12 comments

Comments

@KraToS-zz
Copy link

getting alot of errors when trying to npm install on v3.0.0-rc.0
you can see complete log of this run :
https://paste.ubuntu.com/p/dVQv3fS9Gz/
i tried with node V12 and V13 on windows 10 and ubuntu

@jameswilson
Copy link

jameswilson commented Feb 3, 2020

I'm getting the same errors as the OP, here is a shortened version:

Error 1:

npm WARN tar ENOENT: no such file or directory, open '~/coreui-free-bootstrap-admin-template/node_modules/.staging/request-1a2d42e9/index.js'
...
[lots more errors like this]
...
npm WARN tar ENOENT: no such file or directory, open '~/coreui-free-bootstrap-admin-template/node_modules/.staging/lodash-6a94ce82/lodash.min.js'

Error 2:

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@coreui/chartjs/-/chartjs-2.0.0.tgz
npm ERR! 404 
npm ERR! 404  '@coreui/[email protected]' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'coreui-free-bootstrap-admin-template'

Steps I followed:

$ git clone [email protected]:coreui/coreui-free-bootstrap-admin-template.git
$ cd coreui-free-bootstrap-admin-template
$ git checkout v3-next
$ npm run build-clean
$ npm run build

Environment:

MacOS Mojave 10.14.6

$ node --version
v12.14.1
$ npm --version
6.13.4
$ npm version
{
  '@coreui/coreui-free-bootstrap-admin-template': '3.0.0-rc.0',
  npm: '6.13.4',
  ares: '1.15.0',
  brotli: '1.0.7',
  cldr: '35.1',
  http_parser: '2.8.0',
  icu: '64.2',
  llhttp: '2.0.1',
  modules: '72',
  napi: '5',
  nghttp2: '1.40.0',
  node: '12.14.1',
  openssl: '1.1.1d',
  tz: '2019c',
  unicode: '12.1',
  uv: '1.33.1',
  v8: '7.7.299.13-node.16',
  zlib: '1.2.11'
}

@jameswilson
Copy link

Upgrading to node 13.7.0 and re-running npm run build fixed the first errors regarding npm WARN tar ENOENT no such file or directory, however the second error message is still there. Additionally there are few deprecation warnings, that should probably be resolved before releasing the 3.0.0 version.

npm WARN deprecated [email protected]: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated @types/[email protected]: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@coreui%2fchartjs - Not found
npm ERR! 404 
npm ERR! 404  '@coreui/chartjs@^2.0.0' is not in the npm registry.

@jameswilson
Copy link

I should clarify, that though the install function didnt have the ENOENT error, the npm run build command did have some issues (see below). I think basically because of the 404 issue, it prevented continuing to install the rest of the dependencies.

$ npm run build

> @coreui/[email protected] build /Users/jameswilson/App/ProcesoElectronico/coreui-free-bootstrap-admin-template
> npm-run-all build-clean --parallel css js copy --sequential build-vendors

sh: npm-run-all: command not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! @coreui/[email protected] build: `npm-run-all build-clean --parallel css js copy --sequential build-vendors`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the @coreui/[email protected] build script.

@xidedix
Copy link
Member

xidedix commented Feb 3, 2020

@KraToS-zz @jameswilson
@coreui/[email protected] was set private by mistake. Sorry for the inconvenience.
It should work fine now.

@jameswilson
Copy link

Thanks @xidedix , this fixed it for me. Cheers, have a great week.

@KraToS-zz
Copy link
Author

thanks for fixing this
but is it possible to have asidebar and sidebar like demo version ?

@baradhili
Copy link

I'm seeing issue running npm install and npm run build on the current release as well as the downloaded zip
running within a homestead environment but as a plain HTML

`vagrant@homestead:~/code$ npm install
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/rc):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ENOTEMPTY: directory not empty, rmdir '/home/vagrant/code/node_modules/fsevents/node_modules/.rc.DELETE/node_modules'

npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/vagrant/code/node_modules/@babel/runtime/node_modules/regenerator-runtime/package.json.155718331
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/vagrant/code/node_modules/@babel/runtime/node_modules/regenerator-runtime/package.json.155718331'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /home/vagrant/.npm/_logs/2020-08-06T06_21_35_997Z-debug.log
`

and
`vagrant@homestead:~/code$ npm run build

@coreui/[email protected] build /home/vagrant/code
npm-run-all build-clean --parallel css js copy --sequential build-vendors

sh: 1: npm-run-all: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! @coreui/[email protected] build: npm-run-all build-clean --parallel css js copy --sequential build-vendors
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the @coreui/[email protected] build 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! /home/vagrant/.npm/_logs/2020-08-06T06_27_20_863Z-debug.log
`

@javiqn
Copy link

javiqn commented Dec 10, 2020

Same error here... Any solution with the package directly downloaded from the official website?

@relesssar
Copy link

same problem npm install fail, and --force also

git clone https://github.com/coreui/coreui-free-react-admin-template.git my-project

Cloning into 'my-project'...
remote: Enumerating objects: 125, done.
remote: Counting objects: 100% (125/125), done.
remote: Compressing objects: 100% (71/71), done.
remote: Total 3938 (delta 26), reused 76 (delta 17), pack-reused 3813Receiving objects: 100% (3938/3938), 1.05 MiB | 2.0Receiving objects: 100% (39
38/3938), 2.70 MiB | 3.27 MiB/s, done.
Resolving deltas: 100% (1481/1481), done.

>cd my-project

\my-project>npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN Found: [email protected]
npm WARN node_modules/react
npm WARN   react@"^17.0.1" from the root project
npm WARN   9 more (@coreui/icons-react, @coreui/react, react-dom, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer react@"0.13.x || 0.14.x || ^15.0.0-0 || ^16.0.0-0" from [email protected]
npm WARN node_modules/enzyme-adapter-utils
npm WARN   enzyme-adapter-utils@"^1.13.1" from @wojtekmaj/[email protected]
npm WARN   node_modules/@wojtekmaj/enzyme-adapter-react-17
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^17.0.1" from the root project
npm ERR!   peer react@"^17.0.1" from @coreui/[email protected]
npm ERR!   node_modules/@coreui/icons-react
npm ERR!     @coreui/icons-react@"^1.0.2" from the root project
npm ERR!     @coreui/icons-react@"^1.1.0" from @coreui/[email protected]
npm ERR!     node_modules/@coreui/react
npm ERR!       @coreui/react@"^3.4.0" from the root project
npm ERR!   8 more (@coreui/react, react-dom, react-router-dom, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^0.14 || ^15.0.0 || ^16.0.0-alpha" from [email protected]
npm ERR! node_modules/enzyme-adapter-utils/node_modules/airbnb-prop-types
npm ERR!   airbnb-prop-types@"^2.16.0" from [email protected]
npm ERR!   node_modules/enzyme-adapter-utils
npm ERR!     enzyme-adapter-utils@"^1.13.1" from @wojtekmaj/[email protected]
npm ERR!     node_modules/@wojtekmaj/enzyme-adapter-react-17
npm ERR!       @wojtekmaj/enzyme-adapter-react-17@"^0.3.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\nova\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\..\2021-03-30T11_26_38_737Z-debug.log

@Raheel1258
Copy link

Raheel1258 commented Jan 12, 2022

I'm have an issue when, I run npm run build command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @coreui/[email protected] build: react-scripts build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @coreui/[email protected] build 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! /Users/macbook/.npm/_logs/2022-01-12T09_07_30_672Z-debug.log

@iz5clj
Copy link

iz5clj commented Jan 12, 2022

Check your node version (node -v)
Sometimes newest version of node are not compatible.
I use nvm (node version manager) and I switch to node v 15 or even 14 sometimes to install some repos.
Hope that helps.

@mrholek
Copy link
Member

mrholek commented Jan 12, 2022

@Raheel1258 we fixed those issues in v3.2.2, you should upgrade it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants