This is error
npm WARN bootstrap#4.0.0-beta.2 requires a peer of popper.js#^1.12.3 but none is installed. You must install peer dependencies yourself.
How can I solve this error?
Peer dependencies are NO LONGER INSTALLED AUTOMATICALLY from version 3.0
https://github.com/npm/npm/releases/tag/v3.0.0
You have to install it manually and make it part of your npm package.
npm install popper.js#^1.12.3 --save
Related
I recently created a new laravel 8 project using Breeze for the authentication and tailwind css. All worked perfectly when running npm run watch but once I run npm run prod I ran into errors. I noticed that the Tailwind docs mention that there are PostCSS issues so you need to unistall and run
npm install tailwindcss#npm:#tailwindcss/postcss7-compat #tailwindcss/postcss7-compat postcss#^7 autoprefixer#^9
I done that however every time I run npm run prod now the build quits at 98% and says
Additional dependencies must be installed. This will only take a moment.
Running: npm install postcss#^8.1 --save-dev --legacy-peer-deps
npm WARN browser-sync-webpack-plugin#2.2.2 requires a peer of webpack#^1 || ^2 || ^3 || ^4 but none is installed. You must install peer dependencies yourself.
Finished. Please run Mix again.
This auto updates PostCSS to 8.1 every time.
After that if I run npm run prod again it does the exact same message over and over.
I've tried removing the browsersync plugins and trying again but it still doesn't work.
Anyone ran into this or got a solution?
laravel-mix v6 now supports PostCSS8
According to tailwind docs, it suggests to use npm install tailwindcss#npm:#tailwindcss/postcss7-compat #tailwindcss/postcss7-compat postcss#^7 autoprefixer#^9
With the new Mix v6, run npm install tailwindcss#latest postcss#latest autoprefixer#latest
After this, npm run prod will run the way it should.
you must upgrade laravel mix using the following command
npm install laravel-mix#latest
As Digvijay mentioned above the new Mix v6 now supports PostCSS 8. So run:
npm install tailwindcss#latest postcss#latest autoprefixer#latest
After the when you run npm run prod you will still get this message:
Additional dependencies must be installed. This will only take a moment.
Running: npm install browser-sync browser-sync-webpack-plugin#2.2.2 --save-dev --legacy-peer-deps
npm WARN browser-sync-webpack-plugin#2.2.2 requires a peer of webpack#^1 || ^2 || ^3 || ^4 but none is installed. You must install peer dependencies yourself.
Finished. Please run Mix again.
To fix this just add sudo to the front of the npm command it ran:
sudo npm install browser-sync browser-sync-webpack-plugin#2.2.2 --save-dev --legacy-peer-deps
Now run npm run prod and it should work!
I am installing the CLI Tools for a local Hyperledger Composer dev environment on a MacBook Pro (MacOS 10.13.2) and have deprecation / package name change messages come up in the output from NPM. To do the install I am following the instructions from this location:
https://hyperledger.github.io/composer/installing/development-tools.html
My question is do I need to take action based on these messages (see below), or can I just continue? Please forgive the basic question, but am a total newb at this level of work on a Mac - am doing it for a Hyperledger course on Coursera.org.
This is the command that I run: npm install -g composer-cli
...and here are the first few lines of output:
npm WARN deprecated fs-promise#1.0.0: Use mz or fs-extra^3.0 with Promise Support
npm WARN deprecated crypto#0.0.3: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
npm WARN deprecated jade#1.11.0: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated transformers#2.1.0: Deprecated, use jstransformer
npm WARN deprecated nodemailer#2.7.2: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
then a little further down I get this:
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
Update (2018-01-11)
Am continuing following Joe Clay's reply below and now just run this command: npm install -g composer-playground
...and get the following warnings at the end of the output from NPM:
npm WARN ngx-clipboard#8.0.4 requires a peer of #angular/core#>=4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-clipboard#8.0.4 requires a peer of #angular/common#>=4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-clipboard#8.0.4 requires a peer of #angular/platform-browser#>=4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-clipboard#8.0.4 requires a peer of core-js#>=2.4.1 but none is installed. You must install peer dependencies yourself.
npm WARN #ng-bootstrap/ng-bootstrap#1.0.0-beta.2 requires a peer of #angular/core#^4.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN #ng-bootstrap/ng-bootstrap#1.0.0-beta.2 requires a peer of #angular/common#^4.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN #ng-bootstrap/ng-bootstrap#1.0.0-beta.2 requires a peer of #angular/forms#^4.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-window-token#0.0.2 requires a peer of #angular/core#>=2.4.1 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-window-token#0.0.2 requires a peer of #angular/common#>=2.4.1 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-window-token#0.0.2 requires a peer of #angular/platform-browser#>=2.4.1 but none is installed. You must install peer dependencies yourself.
npm WARN ngx-window-token#0.0.2 requires a peer of core-js#>=2.4.1 but none is installed. You must install peer dependencies yourself.
Will continue for now and see if these warnings affect the final dev env't. Am a bit disappointed with the IBM crowd for giving code like this to students :(
Thanks muchly in advance for your help!
cheers, Lawrence
Endorsing Joe Clay's response, you can ignore those messages as he has articulated. peerDependencies is defined in package.json (referring to the Angular messages, which Playground depends on).
Hyperledger consists of a number of members (not just IBM please note) - see more here -> https://www.hyperledger.org/members that contribute code to projects such as Hyperledger Compoer (one such incubation project)
I installed a module using npm:
npm install highlightjs --save
Then I imported it inside my app.js:
import "highlightjs"
When I run mix phoenix.server, I get this error in the console:
error: Resolving deps of web/static/js/app.js failed. Could not load module 'highlightjs' from '/Users/[path]/web/static/js'. Possible solution: run npm install.
Obviously, running npm install doesn't fix it, since it's already installed.
Versions:
Brunch: 2.7.4
Phoenix: 1.2.1
I'm getting this error while doing gulp build task after installing "bangular" project (yo bangular).
Error: libsass bindings not found. Try reinstalling node-sass?
seems like this is because of the latest node, python versions
To resolve this:
I have pointed the environment variable PYTHON to python27 binary
npm uninstall node-sass
npm install node-sass#latest
npm uninstall gulp-sass
npm install gulp-sass#latest
also, deleted global node-gyp module (from /nodejs/node_modules/npm/node_modules/ dir) and re-installed (npm install -g node-gyp#latest).
I'm trying to install docpad and following the guide on: http://docpad.org/docs/install
When I issue the command:
npm install -g docpad#6.63
I get the following npm error:
npm ERR! Error: No compatible version found: taskgroup#'~3.3.7n'
npm ERR! Valid install targets:
npm ERR! ["2.0.0","3.0.0","3.1.0","3.1.1","3.1.2","3.2.0","3.2.2","3.2.3","3.2.4","3.3.0","3.3.1","3.3.2","3.3.3","3.3.4","3.3.5","3.3.6","3.3.7","3.3.8"]
My node version: v0.10.15
My npm version: 1.2.18
I'm running Kubuntu 13.10 with all updates.
I checked if there is an issue reported for this on github, there isn't. Should I report this as an issue or am I doing something wrong?
Same problem here (Kubuntu 13.10).
I sugggest to go back to a previous version of docpad for the moment. On Ubunto/Debian there is another pitfall: some node modules depend on the nodejs executable to be available under node, so you need the additional package nodejs-legacy.
This worked for me:
sudo apt-get install nodejs-legacy
npm install docpad#6.55.6
Bug on DocPad's behalf, that n shouldn't have been there. Now fixed in v6.63.5. Thanks for the report!