[tools] Migrate to new npm version tool#616
Merged
oliviertassinari merged 3 commits intomasterfrom Aug 30, 2025
Merged
Conversation
Bundle size report
|
e019d9c to
96f0475
Compare
96f0475 to
bb994e9
Compare
bb994e9 to
c546e05
Compare
Janpot
approved these changes
Aug 30, 2025
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.
How it looks in this PR:
In the future, I guess we could add HTTP 301, but I'm unclear on how to do this. Actually, I would rather stick to this client side redirection (
<Redirect>) so it's very visible once we kill the subdomain that those link will break.One step of #502, just to force myself to stop using this old pie chart 😄
Preview: https://mui-tools-public-pr-616.onrender.com/prod/pages/npmVersion