New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: Upgrade pipelines to Node18 + upgrade nvm recommendation #17389
Conversation
This reverts commit 314a286.
cf75066
to
a9d1c81
Compare
|
package-lock.json was changed from lock file format 1 to 3. This seems like a bad change since you are trying to stay on the same npm version. Probably revert that file. |
b779d13
to
684b4bf
Compare
This reverts commit 8946495.
This reverts commit f768ba6.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work getting the CI to pass! I think you can merge now. :) Even if we need to upgrade npm, we can do that separately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few things to comment on or make sure are required changes from me.
Without doing new npm, package-lock.json should probably go back too as Craig suggested.
I was able to revert all of these file to their package-lock.json I suggest reverting those files and seeing if CI still passes. |
|
CI did fail on examples/apps/view-framework-sampler/src/views/reactView.tsx which is what I had seen too. I don't know how your build worked, Tyler. Of course I don't know why it actually fails either. Mysteries of lerna managed dependencies. Home stretch. In reply to: 1743993967 |
|
The packages/test/test-end-to-end-tests/src/test/deRehydrateContainerTests.spec.ts file was not reverted because that fix and e2e test that hangs. |
Update the recommended versions of Node.js for developers to use, as well as the version used by CI, from version 14 to 18.
This change made some scenarios in some e2e tests hang, so a fix for skipping them had to be included.
Details:
0.58.x doesn't have the fix to routerlicious-driver in this PR: #8913
(also see related issue for more context on the problem: #9163)
This causes this test to hang while loading container2, as the snapshot is over 16KB.