Upgrade dependencies to latest semver/major versions, fix rollup-plug… - #156
Draft
BenjaminTruong-okta wants to merge 3 commits into
Draft
Upgrade dependencies to latest semver/major versions, fix rollup-plug…#156BenjaminTruong-okta wants to merge 3 commits into
BenjaminTruong-okta wants to merge 3 commits into
Conversation
…in-replace delimiters regression
Newer node-releases (>=2.0.45, pulled in transitively via browserslist) declares engines.node >=18, which breaks yarn install --frozen-lockfile on CI's pinned Node 16.20.2.
Node 16 is EOL and was requiring a node-releases resolution pin to keep yarn install from failing on newer transitive dependencies.
This file contains hidden or 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
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.
…in-replace delimiters regression
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Reviewers