te-online / timemanager

TimeManager App within Nextcloud to manage time tracking.
GNU Affero General Public License v3.0
95 stars 19 forks source link

Deprecated dev dependencies #183

Closed raph-topo closed 1 week ago

raph-topo commented 1 week ago

Hello, I'm looking into contributing to this great project, but at installing dev dependencies (package.json in project root), I'm bumping on a number of issues. (package.json in folder tests works fine)

npm install fails, --force shows all errors and GYP build fails also:

❯ npm install --force           
npm warn using --force Recommended protections disabled.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @prettier/plugin-php@0.19.6
npm warn Found: prettier@3.0.0
npm warn node_modules/prettier
npm warn   dev prettier@"^3.0.0" from the root project
npm warn   1 more (eslint-plugin-prettier)
npm warn
npm warn Could not resolve dependency:
npm warn peer prettier@"^1.15.0 || ^2.0.0" from @prettier/plugin-php@0.19.6
npm warn node_modules/@prettier/plugin-php
npm warn   dev @prettier/plugin-php@"^0.19.6" from the root project
npm warn
npm warn Conflicting peer dependency: prettier@2.8.8
npm warn node_modules/prettier
npm warn   peer prettier@"^1.15.0 || ^2.0.0" from @prettier/plugin-php@0.19.6
npm warn   node_modules/@prettier/plugin-php
npm warn     dev @prettier/plugin-php@"^0.19.6" from the root project
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@nextcloud/event-bus@3.0.2',
npm warn EBADENGINE   required: { node: '^16.0.0', npm: '^7.0.0 || ^8.0.0' },
npm warn EBADENGINE   current: { node: 'v22.2.0', npm: '10.8.1' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@nextcloud/l10n@2.1.0',
npm warn EBADENGINE   required: { node: '^16.0.0', npm: '^7.0.0 || ^8.0.0' },
npm warn EBADENGINE   current: { node: 'v22.2.0', npm: '10.8.1' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@nextcloud/router@2.0.1',
npm warn EBADENGINE   required: { node: '^16.0.0', npm: '^7.0.0 || ^8.0.0' },
npm warn EBADENGINE   current: { node: 'v22.2.0', npm: '10.8.1' }
npm warn EBADENGINE }
npm warn deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
npm warn deprecated rollup-plugin-node-resolve@5.2.0: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-node-resolve.
npm warn deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm warn deprecated rollup-plugin-babel@4.4.0: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-babel.
npm warn deprecated rollup-plugin-commonjs@10.1.0: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-commonjs.

Should we try updating components or are there some fixed versions necessary for specific reasons?

te-online commented 1 week ago

Hello! I guess I didn’t want to spend time updating build dependencies and bundler configuration.

If you’re using nvm, you can switch to node v16 (nvm use 16), which should work. Also, you can use npm i --legacy-peer-deps instead of --force, I believe. Feel free to update dependencies if you want to spend time on that 😅