Skip to content
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

feat: Upgrade to Node 18 [Feature Branch][JOB-62820] #1141

Merged
merged 11 commits into from
Mar 24, 2023

Conversation

darryltec
Copy link
Contributor

@darryltec darryltec commented Mar 20, 2023

Motivations

Node 14 will not be supported past April 30th so we need to get ahead and upgrade to Node 18.

Changes

Added

Changed

Deprecated

Removed

Fixed

Security

Testing


In Atlantis we use Github's built in pull request reviews.

Random photo of Atlantis

@@ -44,7 +44,7 @@ references:
npm_install: &npm_install
run:
name: Install Dependencies
command: export IGNORE_OPTIONAL_DEPENDENCIES=true; npm ci --no-optional
command: export IGNORE_OPTIONAL_DEPENDENCIES=true; npm ci --no-optional --legacy-peer-deps
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Temporary, just to get us past some hurdles. Delete before merging!

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Mar 20, 2023

Deploying with  Cloudflare Pages  Cloudflare Pages

Latest commit: ae7f9a9
Status: ✅  Deploy successful!
Preview URL: https://bd56d4ff.atlantis.pages.dev
Branch Preview URL: https://upgrade-to-node-18.atlantis.pages.dev

View logs

Darryl Tec and others added 6 commits March 24, 2023 08:25
* build: use NPM workspace instead of Lerna

* fix: workaround npm's lack of topological oder

Basically, npm would run `prepare` on each packages in alphabetical order but components need design to be built first.

This works around that limitation by firing the scripts manually through `npm run [script] -w` which respects the order under `workspaces`

npm/rfcs#548

* fix: reorder scripts for my own sanity

* build: update circle to not look for lock files

* build: use node 18 image on circle ci

* fix: js and css linters

* build: use -omit=optional

* fix: update time test work on node 18

* fix: don't update snaps

* fix: update some snaps

* build: make storybook run on node 18

Thanks @rodrigoeidelvein for the workaround!

* fix: reinstall ts-node

* chore: use lerna recommended setting for symlink

* fix: refix storybook by using js file

* fix: match * on preventManualRelease check
* Update versions in readme

* Update engines in package.json
* Trying build

* Correcting variables

* Removed resource class

Co-authored-by: Darryl Tec <[email protected]>

---------

Co-authored-by: Kingston Fung <[email protected]>
Co-authored-by: Darryl Tec <[email protected]>
@darryltec darryltec marked this pull request as ready for review March 24, 2023 16:53
@darryltec darryltec requested a review from a team March 24, 2023 16:53
Copy link
Contributor

@taylorvnoj taylorvnoj left a comment

Choose a reason for hiding this comment

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

LGTM everything works as expected :shipit: 🚀

@taylorvnoj
Copy link
Contributor

Sorry those conflicts are because of me!

@darryltec darryltec merged commit 8b766cd into master Mar 24, 2023
@darryltec darryltec deleted the upgrade-to-node-18 branch March 24, 2023 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants