Skip to content

Conversation

@MichaIng
Copy link
Member

@MichaIng MichaIng commented Apr 6, 2022

Autoloaders update is required to solve Drone checkers, package-lock.json update to solve all Node checks.

I simply did:

bash build/autoloaderchecker.sh
npm i

PHP version was 8.1, in case it is relevant.

@MichaIng
Copy link
Member Author

MichaIng commented Apr 6, 2022

Strange, package-lock.json is still not in sync:

npm ERR! Missing: react@1.0.0 from lock file
npm ERR! Missing: react-dom@18.0.0 from lock file
npm ERR! Missing: scheduler@0.21.0 from lock file

Looks like those are in package-lock.json but not in package.json, i.e. also no dependencies anymore? I'll try to remove it before npm i.

Ah, now I see a warning, looks like I need to downgrade Node and npm:

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@nextcloud/axios@1.9.0',
npm WARN EBADENGINE   required: { node: '^14.0.0', npm: '^7.0.0' },
npm WARN EBADENGINE   current: { node: 'v17.6.0', npm: '8.5.3' }
npm WARN EBADENGINE }

EDIT: Doesn't change anything. Strange is also that I do not see this error when running npm ci locally with any version. Rebuilding package-lock.json from scratch of course means a lot of bumped dependencies, what we do not want here.

These errors btw showed up the first time with this commit: b404e3f
There must have something changed externally and/or with the GitHub runners environment?

Also I do not understand the error, the two react modules are actual dependencies, e.g.:

    "node_modules/linkifyjs": {
      "version": "2.1.9",
      "resolved": "https://registry.npmjs.org/linkifyjs/-/linkifyjs-2.1.9.tgz",
      "integrity": "sha512-74ivurkK6WHvHFozVaGtQWV38FzBwSTGNmJolEgFp7QgR2bl6ArUWlvT4GcHKbPe1z3nWYi+VUdDZk16zDOVug==",
      "peerDependencies": {
        "jquery": ">= 1.11.0",
        "react": ">= 0.14.0",
        "react-dom": ">= 0.14.0"
      }
    },

And scheduler does exist neither in package-lock.json nor in package.json 😕.

Not idea what is wrong with the CI node checks, I cannot replicate anything locally, help needed.

@szaimen
Copy link
Contributor

szaimen commented Apr 7, 2022

I guess we need some help here. Maybe @artonge has some ideas how to solve this? :)

@artonge
Copy link
Contributor

artonge commented Apr 11, 2022

The issue might come from npm v8.6 npm/cli#4684

@MichaIng
Copy link
Member Author

MichaIng commented Apr 11, 2022

Ah, so the local build was not the issue, but since the workflows installs npm i -g npm@">=7.0.0". This fits to the fact that the CI failures happened the first time without any failing commit/PR merged.

@blizzz blizzz changed the title Update autoloaders and Node package-lock.json [stable23] Update autoloaders and Node package-lock.json Apr 12, 2022
@blizzz blizzz requested review from CarlSchwan and PVince81 April 12, 2022 08:34
Copy link
Member

@blizzz blizzz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rerun the npm step with npm ci for CI

@MichaIng MichaIng force-pushed the update-autoloaders-and-node branch from 29e8c20 to 05f8768 Compare April 12, 2022 21:36
Signed-off-by: MichaIng <micha@dietpi.com>
@MichaIng MichaIng force-pushed the update-autoloaders-and-node branch from 05f8768 to 81af11f Compare April 12, 2022 22:04
@MichaIng
Copy link
Member Author

MichaIng commented Apr 12, 2022

Okay worked now. The three Node modules have now been added to package-lock.json. Please someone with more insights into Node dependencies have a look whether those are the intended versions.

Dependency tree seems to be:

  • linkifyjs
    • react >=0.14.0 => 18.0.0
    • react-dom >=0.14.0 => 18.0.0
      • scheduler ^0.21.0 => 0.21.0

@MichaIng MichaIng requested a review from blizzz April 12, 2022 22:20
@blizzz
Copy link
Member

blizzz commented Apr 13, 2022

@skjnldsv ^

@blizzz blizzz requested a review from skjnldsv April 13, 2022 07:30
@blizzz blizzz mentioned this pull request Apr 13, 2022
@skjnldsv
Copy link
Member

@skjnldsv ^

Honestly can't tell. If linkifyjs requires peerDeps, so be it 🤷

@skjnldsv skjnldsv added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Apr 13, 2022
@skjnldsv skjnldsv merged commit df576c6 into stable23 Apr 13, 2022
@skjnldsv skjnldsv deleted the update-autoloaders-and-node branch April 13, 2022 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to release Ready to be released and/or waiting for tests to finish dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants