PWA-3216 upgrading node to >=18 #4218
Open
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
glo82145
added
the
version: Minor
|
run pr-deploy |
|
Successfully started codebuild job for |
glo82145
force-pushed
the
PWA-3216
branch
2 times, most recently
from
275cc55
to
2c690af
Compare
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.
Description
need to upgrade Node support >=18 for PWA studio package as per Node updates no more availbale for support for lower version as per link https://endoflife.date/nodejs
Prerequisite-
Node >=18 should be installed for PWA setup
Description:
as if now PWA lower support is by default >=14 as per informattion can see on
pwa-studio/package.json
Line 101 in 76fbf76
Actual Result:-
Current Node version support for PWA studio is >=14
Expected:
Default Node version need to be updated in PWA package as >=18
Related Issue
Closes (https://jira.corp.adobe.com/browse/PWA-3216)
Acceptance
Verification Stakeholders
Specification
Verification Steps
Test scenario(s) for direct fix/feature
Test scenario(s) for any existing impacted features/areas
Test scenario(s) for any Magento Backend Supported Configurations
Is Browser/Device testing needed?
Any ad-hoc/edge case scenarios that need to be considered?
Screenshots / Screen Captures (if appropriate)
Breaking Changes (if any)
Checklist