build: modern stack #122
Merged
build: modern stack #122
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
termontwouter
force-pushed
the
build/modern-stack
branch
from
84f33d8 to
6237c35
Compare
termontwouter
force-pushed
the
build/modern-stack
branch
from
15b0236 to
ed67938
Compare
rubensworks
merged commit 557cd41
into
LinkedSoftwareDependencies:master
15 checks passed
|
Nice, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Given that official support for Node.js 14 and 16 has past (their respective end-of-life dates were April 30th and September 11th 2023), I propose we drop support for them in the Components.js stack. Moving to Node.js 18 brings a number of relevant advantages:
fetchAPI!@types/...packages.Note: I first did a bump to Node.js 16 (with Yarn 3). Should we still want to support that version longer, the last commit can be reverted.