npm install
No warnings
npm WARN lifecycle joomla@4.0.0install: cannot run in wd joomla@4.0.0 node build.js --copy-assets && node build.js --build-check (wd=/var/www/html/joomla-cms)postinstall: cannot run in wd joomla@4.0.0 node build.js --compile-js && node build.js --compile-css && node build.js --compile-ce &&cd administrator/components/com_media && npm install && npm run build (wd=/var/www/html/joomla-cms)
npm WARN lifecycle joomla@4.0.0
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
audited 8149 packages in 7.427s
found 10 vulnerabilities (9 low, 1 high)
run npm audit fix
to fix them, or npm audit
for details
Current 4.0-dev Branch on Ubuntu 18.04
I have just rebuilt my system. Joomla is now working. But: I'm worried about the warnings. Did I do something wrong?
$ node --version
v10.13.0
$ npm --version
6.4.1
Labels |
Added:
?
|
fsevents is only for osx - thats why you get an unsupported message on windows and why it is optional (google for more info on what it is used for if you want) so as you are on windows it is normal
@brianteeman Thanks for explaining the fsevents warning.
Title |
|
Labels |
Added:
J4 Issue
|
Can this be closed now?
@dgrammatiko Thank you for your reply. But, my user is the owner of /urs/local.
@brianteeman I just updated my branches and started a new npm install
but I see still see the warnings and vulnerabilities. Are I am the only one?
The vulnerabilities are not a concern. The NPM environment for the CMS is an ecosystem of something like 5000 packages and dependencies of dependencies are locked to older versions of packages with fixed issues. Those issues are in the build/compiler dependencies, if they're even triggered at all.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-11-07 09:16:50 |
Closed_By | ⇒ | brianteeman |
For anyone facing that, seems like a permission related issue.
This is how i solved it:
npm install --unsafe-perm
@astridx Please post node --version and npm --version results.