Fix deps, (because re-rolling the lockfile breaks everything) #680
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
NullVoxPopuli
changed the title
NullVoxPopuli
added
the
internal
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.
All PRs / etc will have failing floating deps tests, due to something like this: https://github.com/typed-ember/glint/actions/runs/7513622017/job/20455581720?pr=680 (in the first run of this PR).
This PR narrows the
@glimmer/*versions to something that works for CJS, as newer@glimmer/*is ESM only.I deleted the lockfile and re-ran yarn, since that was the failing scenario on PRs.
yarn@v1treats^on pre-1.0 versions the same as post-1.0, which is dangerous for@glimmer/*