Update package.json dependencies for new projects

[nenadvicentic]

Currently, after running npx makes aurelia/v1, selecting choices for a new project and running npm install, we immediatelly get warnings about outdates and deprecated npm packages:

√ Please name this new project: » au1-ts-scss-alameda
√ Would you like to use the default setup or customize your choices? » Custom Project
√ App or Plugin? » App
√ Which bundler would you like to use? » CLI's built-in bundler with an AMD module loader
√ Which AMD module loader would you like to use? » Alameda
√ What platform are you targeting? » Web
√ What transpiler would you like to use? » TypeScript
√ How would you like to setup your HTML template? » Minified with htmlmin
√ What css preprocessor would you like to use? » Sass
√ Do you want to add PostCSS processing » Yes
√ Which unit test runner would you like to use? » None
√ Would you like to configure e2e integration testing? » None
√ What is your default code editor? » Visual Studio Code
√ Which features do you want to scaffold into your project? » Minimum
√ Would you like to add a Dockerfile? » No
[makes] Project au1-ts-scss-anaconda has been created.
√ Do you want to install npm dependencies now? » Yes, use npm
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated @babel/plugin-proposal-class-properties@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm warn deprecated @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm warn deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.

Would it be possible to update npm dependencies, perhaps also using gulp@5 for aureli-cli projects?

[3cp]

I will try upgrade all deps. Gulp v5 is dangerous. Lots of gulp plugins do not play well with it. Last time we tried, gulp-typescript did not work.

[3cp]

Other deps were upgraded. Next, I will upgrade eslint to v9. Then try gulp v5 again.

[3cp]

eslint is upgraded to v9. I will skip gulp v5, as I can see there are still many unfixed v5 issues in the gulp repo.

[nenadvicentic]

@3cp Thank you for the quick reaction.

I tried to create a new local project. The project itself and it's own package.json are really nice now! Much better.

However, I am still getting similar warnings:

√ Do you want to install npm dependencies now? » Yes, use npm
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated @babel/plugin-proposal-class-properties@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)

added 874 packages, and audited 875 packages in 22s

I am also getting a warning during au build (it was there also when I initially wrote the ticket):

Finished 'processCSS'
(node:37956) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)
Finished 'processMarkup'

Looking into more details, the packages that give warning are not even listed in the project itself. And judging by @babel/plugin-proposal-class-properties warning, it seems like this packages are part of aurelia-cli dependencies.

I guess that aurelia-cli is more complex project compered. Is there any chance that this project gets updated too at some point?

[3cp]

That's not right. I will check and fix. Thanks for details!

[3cp]

aurelia/cli#1210