Update dependencies & fluent-react/example #612
Merged
Conversation
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
|
Thanks for this! Could this also be released as a new version? |
dj-sf
pushed a commit
to djsf-kobayashi/penny
that referenced
this pull request
Sep 30, 2023
@fluent/react lists 0.17 as the latest compatible version of @fluent/bundle. A fix has been merged, but not released yet: projectfluent/fluent.js#612
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.
Fixes #610, as the fluent-react
peerDependencycondition was indeed too strict.With modern
npm, we don't need to usefile:paths for internal dependencies and can also drop support ofnpm<7in the lockfile.