Without knowingly changing anything, all of a sudden today I started getting a huge amount of warnings related to NPM 3.5.1 every time I build. Anyone have any idea why or how I can get rid of or suppress them?
If it matters, it's happening launching a Meteor app (via the Meteor command) built using webpack...
************UPDATE: 12/10/15****************
OK, I figured out what is going on now, but not quite sure how to 'fix' it. The system (which BTW is Windows 10) has NPM 3.51 installed by the project has a symlink to the node_modules directory so cannot be updated there.
Does anyone know how to get around this? I tried going into the directory and running update from there and that fails too. Is there a way to remove a symlink in Windows, do the update, then put it back?
Any help is more than appreciated because there are literally hundreds of warnings and and I can't see the relevant console output (or scroll back up to it because it's out of the display buffer). This is really hindering my progress.
TIA!
npm WARN In npm#3.5.1 replacing bundled version of lodash.repeat with lodash.rep
eat#3.0.1
npm WARN In npm#3.5.1 replacing bundled version of lodash._basetostring with lod
ash._basetostring#3.0.1
npm WARN In npm#3.5.1 replacing bundled version of lodash.repeat with lodash.rep
eat#3.0.1
npm WARN In npm#3.5.1 replacing bundled version of lodash._basetostring with lod
ash._basetostring#3.0.1
npm WARN In npm#3.5.1 replacing bundled version of lodash.repeat with lodash.rep
eat#3.0.1
npm WARN In npm#3.5.1 replacing bundled version of once with once#1.3.2
npm WARN In npm#3.5.1 replacing bundled version of opener with opener#1.4.1
npm WARN In npm#3.5.1 replacing bundled version of os-homedir with os-homedir#1.
0.1
npm WARN In npm#3.5.1 replacing bundled version of os-tmpdir with os-tmpdir#1.0.
1
npm WARN In npm#3.5.1 replacing bundled version of path-is-inside with path-is-i
nside#1.0.1
npm WARN In npm#3.5.1 replacing bundled version of mute-stream with mute-stream#
0.0.5
npm WARN In npm#3.5.1 replacing bundled version of read-cmd-shim with read-cmd-s
him#1.0.1
npm WARN In npm#3.5.1 replacing bundled version of util-extend with util-extend#
1.0.1
npm WARN In npm#3.5.1 replacing bundled version of jju with jju#1.2.1
npm WARN In npm#3.5.1 replacing bundled version of read-package-tree with read-p
ackage-tree#5.1.2
npm WARN In npm#3.5.1 replacing bundled version of readdir-scoped-modules with r
eaddir-scoped-modules#1.0.2
npm WARN In npm#3.5.1 replacing bundled version of realize-package-specifier with...
Related
I'm very new to js and trying to set up canvas-sketch, but keep getting this:
I updated in terminal using 'npm install --save core-js#^3' and am getting this still:
madeleinesanchez#Madeleines-MacBook-Pro ~ % npm install --save core-js#^3
up to date, audited 544 packages in 885ms
69 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
madeleinesanchez#Madeleines-MacBook-Pro ~ % npm install canvas-sketch-cli -g
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated core-js#2.6.12: core-js#<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
changed 541 packages, and audited 542 packages in 11s
68 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
madeleinesanchez#Madeleines-MacBook-Pro ~ %
I've tried all kinds of workarounds but maybe am doing something wrong. Send help! lol thank you
Tried npm install --save core-js#^3, npm install --save core-js#^3, npm cache clean, npm update. I also tried npm uninstall core-js and then npm i core-js
I was expecting to stop recieving warnings about the old version after updating it.
can somebody help me? I'd like to install Firebase.
But I became a lot of message, like these:
npm WARN deprecated source-map-resolve#0.5.3: See ...
npm WARN deprecated chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated resolve-url#0.2.1: .....
npm WARN deprecated circular-json#0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated left-pad#1.3.0: use String.prototype.padStart()
npm WARN deprecated acorn-dynamic-import#3.0.0: This is probably built in to whatever tool you're using. If you still need it... idk
etc. etc.
and I use this version of npm:PS C:\Users\otthon\haduzenet2\index>
npm -v
9.4.0
and node.js:PS C:\Users\otthon\haduzenet2\index>
node -v
v18.13.0
and the latest version for npm is:" a package manager for JavaScript. Latest version: 9.4.0, last published: 5 days ago."
My question: why are there so many deprecated components of npm?
What commands must I follow on the command line to downgrade. I ran uninstall and reinstalled as well as nom i -S firebase#... but now when I reload the app it just crashes.
If you have to install an older version of a package, just specify it
npm install <package>#<version>
For example: npm install firebase#9.2.0
You can also add the --save flag to that command to add it to your package.json dependencies, or --save --save-exact flags if you want that exact version specified in your package.json dependencies.
The install command is documented here: https://docs.npmjs.com/cli/install
If you're not sure what versions of a package are available, you can use:
npm view firebase versions
And npm view can be used for viewing other things about a package too.
https://docs.npmjs.com/cli/view
don't forget to remove .lock file first to rebuilt the depedency
can u give the error messege for us....
i was installing asp.net in my ubuntu system , the following command was not executed because "bower" was outdated
$ npm install -g yo bower grunt-cli gulp generator-aspnet
npm WARN deprecated bower#1.8.8: We don't recommend using Bower for new projects. Please consider Yarn and Webpack or Parcel. You can read how to migrate legacy project here: https://bower.io/blog/2017/how-to-migrate-away-from-bower/
npm WARN deprecated generator-aspnet#0.3.3: Use dotnet new instead
npm WARN deprecated gulp-util#3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated samsam#1.1.2: This package has been deprecated in favour of #sinonjs/samsam
npm WARN deprecated formatio#1.1.1: This package is unmaintained. Use #sinonjs/formatio instead
npm WARN deprecated cross-spawn-async#2.2.5: cross-spawn no longer requires a build toolchain, use it instead
so how can i replace bower and grunt with alternatives ?
You don't have to use Yeoman to create asp .net project. In warning you have information what to do: npm WARN deprecated generator-aspnet#0.3.3: Use dotnet new instead npm WARN Just use dotnet CLI. You can create empty asp .net project just using dotnet new web in your shell and that's all.
While installing grunt, one of the errors is unmet dependency semver#4
i am using node#0.10.33, npm#1.4.28
i run two commands and it shows two versions and one is invalid
npm list -g
and in the tree it shows semver#2.3.0 invalid
now i run
npm view semver version
now it shows 4.1.0
i tried npm update semver
but nothing happens
i have even tried to the solution provided in similar question npm error invalid semver
curl https://npmjs.org/install.sh | sh
but donesnt help
I am new to npm and grunt please help!
what do you mean by While installing grunt?
Installing the grunt-cli tools or the grunt-runner in your project?
since 4.0 grunt is split into 2 modules:
grunt-cli
grunt
grunt-cli needs to be installed globally, and only 1 time:
$ npm install grunt-cli -g
grunt needs to be installed locally in every project where you want to use grunt and grunt-plugins:
$ npm install grunt
updating npm:
the crazy stuff about npm is, that you can even update npm via npm:
$ npm update npm -g
the current npm version is 2.1.9, so maybe this solves your problem.
hint: use nvm vor node.js version management. this solves multiple problems:
easy version switching
you don't need sudo for global packages