Npm packages

Why are these warning in the latest ionic, fresh app building…
Is there a way to remove all these…

npm i
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated urix@0.1.0: Please see GitHub - lydell/urix: [DEPRECATED] Makes Windows-style paths more unix and URI friendly.
npm WARN deprecated resolve-url@0.2.1: GitHub - lydell/resolve-url: [DEPRECATED] Like Node.js’ `path.resolve`/`url.resolve` for the browser.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See There’s Math.random(), and then there’s Math.random() · V8 for details.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See There’s Math.random(), and then there’s Math.random() · V8 for details.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See There’s Math.random(), and then there’s Math.random() · V8 for details.
npm WARN deprecated querystring@0.2.0: The
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142

added 1620 packages, and audited 1621 packages in 4m

When you create an Ionic Angular app, it includes a lot of dependencies out of Ionic control and those warnings come from those dependencies.
I’ve checked a few of the warnings you mention and they come from angular packages, webpack or the dev server.

I wouldn’t worry about too much warnings, they are usually harmless, and when they become a problem they will probably be fixed.

1 Like

I am afraid as they may become big headache, when we don’t upgrade them timely or if there are any security flaws found.

Is it possible for us to independently upgrade default ionic project angular, ts versions…

currently it uses

image

would any upgrade to these verstion have possibility of breaking ionic?

b.t.w I come from this below thinking…

The angular dependencies that had the dependencies with warnings are actually build related and are in the devDependencies section, like @angular-devkit/build-angular, or @angular/cli. None of those should make your app vulnerable.

But yeah, you can always update your app dependencies. As long as they are minor version bumps it shouldn’t cause problems with Ionic. When they are major version bumps then sometimes (not always), they need changes on Ionic.

1 Like