Repository navigation
fix(twake-mui): Accept twake-icons 3 in the devDependencies - #221
Merged
Merged
Conversation
twake-icons went to 3.0.0 and ^2.10.0 no longer matched the workspace, so npm ci looked for 2.17.0 from the registry and failed on the lock file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
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.
The release of `@linagora/twake-icons` 3.0.0 broke `npm ci` on main (run): twake-mui's devDependency `^2.10.0` no longer matched the workspace, so npm wanted 2.17.0 from the registry, which is missing from the lock file.
Checked locally with `npm ci` and `npm run build`.
🤖 Generated with Claude Code