Does "au new" need an upgrade?

New to Aurelia. My node is version v12.9.1.
Following the tutorial, starting with “au new”.
At the last step, when it installs the node dependencies, it appears that the package.json
file generated is way out of date, because I get the following warnings:

npm WARN deprecated request@2.88.2: request has been deprecated, see

npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

npm WARN aurelia-tools@2.0.0 requires a peer of babel-eslint@^7.2.3 but none is installed. You must install peer dependencies yourself.

npm WARN aurelia-tools@2.0.0 requires a peer of eslint@^4.0.0 but none is installed. You must install peer dependencies yourself.

npm WARN acorn-jsx@5.2.0 requires a peer of acorn@^6.0.0 || ^7.0.0 but none is installed. You must install peer dependencies yourself.

Fixing all of these is not that hard, but shouldn’t the CLI project creation process work without
a lot of manual “fixing”? I would expect this to “just work”!


I agree, but it might be because development is focused on Aurelia V2. Maybe open an issue/PR on the Aurelia V1 CLI github project so its on their radar?

1 Like

Thanks for the valid concern!

request v2 is a dep of outdated jsdom for aurelia-pal-nodejs and jest, I will try to move them to latest version.
Our aurelia-tools needs to update to latest tooling too.

I don’t know how you got acorn-jsx. Can you show me the full console log of your au new?

Update: stale PR merged and released, will be reflected in app skeleton of next cli release.

Update: aurelia-tools can be removed from our skeleton merged, as we only use it in eslint config "extends": "./node_modules/aurelia-tools/.eslintrc.json",, personally, I only use "extends": "eslint:recommended", with few additional rules.


That’s interesting, does that mean I can drop it from my plugin Aurelia-Slickgrid on this line since I built it with TypeScript and tslint?


Pretty sure ts project doesn’t need it.


ok thanks, will give that a try :+1:


Removed aurelia-tools, ran the lib, ran all the unit tests and everything is fine… all good!
Dang all this time I thought there was some special tools like a Jedi light saber :dagger: hidden in this toolset but at the end it’s not needed at all and perhaps the name wasn’t what it represent lol


@frodeaux we are working on a new cli release to not only clean up those warnings as much as possible, also bring up all 3rd-party deps to latest as much as possible.


aurelia-cli v1.3.0 is released with updated deps.

But :confused: jsdom v15 still uses deprecated request v2.88.2. There is no much we can do about the deep dependency of 3rd-party tools.

Note we didn’t move to latest jsdom v16 because of nodejs 8 support. Latest jest also stayed on jsdom v15 for the same reason.