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.

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

Error installing AdminLTE v3-rc4 via npm #2317

Closed
1 of 3 tasks
diegoldev opened this issue Oct 9, 2019 · 7 comments
Closed
1 of 3 tasks

Error installing AdminLTE v3-rc4 via npm #2317

diegoldev opened this issue Oct 9, 2019 · 7 comments

Comments

@diegoldev
Copy link

Issue type:

  • Feature request
  • Bug report
  • Documentation

Environment:

  • AdminLTE Version: v3-rc4
  • Operating System: Debian Docker over Windows 10 x64 host
  • Browser (Version): N/A

Description:

When you trying to install AdminLTE v3 vía npm as described in documentation
npm install admin-lte@v3-latest --save
It's throwing an error like this:

npm ERR! code ELIFECYCLE
npm ERR! errno 243
npm ERR! [email protected] install: npm run plugins
npm ERR! Exit status 243
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

I've tried cleaning and reinstall with this command:
npm cache clean --force && rm -rf node_modules && rm ./package-lock.json && npm install
But was not successfull

Here is a more detailed StackTrace:

36407 verbose stack Error: [email protected] install: npm run plugins
36407 verbose stack Exit status 243
36407 verbose stack at EventEmitter. (/home/laradock/.nvm/versions/node/v12.9.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
36407 verbose stack at EventEmitter.emit (events.js:209:13)
36407 verbose stack at ChildProcess. (/home/laradock/.nvm/versions/node/v12.9.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
36407 verbose stack at ChildProcess.emit (events.js:209:13)
36407 verbose stack at maybeClose (internal/child_process.js:1021:16)
36407 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)

@REJack
Copy link
Collaborator

REJack commented Oct 9, 2019

I found a similar issue on github, the issue author closed his issue with this:

This ended up looking to be a permissions issue.
element-hq/element-web#7458

The npm error say also "This is probably not a problem with npm".
Please check if your permission are correct 😄

@diegoldev
Copy link
Author

diegoldev commented Oct 9, 2019 via email

@REJack
Copy link
Collaborator

REJack commented Oct 9, 2019

The difference between rc.1 and rc.4 is that the plugins come not within the npm package, caused they are in the package.json and will installed with adminlte and for this is the plugins script, may I will remove it from install scripts to avoid this errors.

@diegoldev
Copy link
Author

diegoldev commented Oct 10, 2019

Well, finally I could install rc.4 via npm. Effectively, It was a permission issue.
npm had not access to /root/.npm dir
I've set grant access to that dir and installation was succesfull. I don't know if there's a better solution. In official page suggests this one. But, sincerely I don't know if works.

Edit:
One more thing I forget: I also added the arg: --cache /tmp/empty-cache to command:
npm install admin-lte@v3-latest --save --cache /tmp/empty-cache

@REJack
Copy link
Collaborator

REJack commented Oct 16, 2019

I close this issue 😄

@REJack REJack closed this as completed Oct 16, 2019
@bobvandevijver
Copy link

@REJack I just experienced some problems with yarn, as somehow the plugins folder no longer contained the plugin I was expecting (this was due to the fact that it was downgraded to v2 by mistake, so no direct connection with this particular issue).

I think it would indeed be wise to remove the custom install script for the plugins, and make users aware that they should link the assets from the node_modules directly if required.

@ajewole
Copy link

ajewole commented Mar 26, 2021

I had similar issue

@ColorlibHQ ColorlibHQ locked as too heated and limited conversation to collaborators Mar 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants