-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[docs] Upgrade next to v9 #16546
[docs] Upgrade next to v9 #16546
Conversation
@material-ui/core: parsed: -0.54% 😍, gzip: -0.66% 😍 Details of bundle changes.Comparing: 95cbe4f...7b09a56
|
ddc629e
to
8520640
Compare
no longer needed
Number.NaN is serialized as `null`
8520640
to
23a1284
Compare
b36c39d
to
8a4ab7e
Compare
* parses output from next build to size snapshot format | ||
* @returns {[string, { gzip: number, files: number, packages: number }][]} | ||
*/ | ||
async function getNextPagesSize() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to keep track of all the documentation pages? If I could trade all the documentation pages with all the components bundle size, I would :).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to keep track of all the documentation pages?
It helps spotting ES modules issues
If I could trade all the documentation pages with all the components bundle size, I would :).
You don't need to trade them. Just add them to the tracking.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It helps spotting ES modules issues
Ok, I was assuming that tracking some key pages, like the home and the button, text field pages would be enough to fix systematic problems.
My question had the following background motivation: tracking all the documentation pages opens the door to optimize specific pages in particular. I don't think it would yield the best return on our time. So I was wondering if we could not collect the data to prevent this in the first place.
However, the counter-argument to it is that we might spot some pages that have an abnormal bundle size, most likely related to third-party libraries we bundle, from the demos. Given that people copy & paste the demos, our users will be impacted too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tracking all the documentation pages opens the door to optimize specific pages in particular. I don't think it would yield the best return on our time. So I was wondering if we could not collect the data to prevent this in the first place.
Yeah we need to moderate ourselves if it comes to that. But specifically #16046 will target various pages. Only tracking pages with demos might make more sense but then other things might fall through the cracks.
I'd rather have the data available and then limit the view if it becomes to noisy instead of limiting the data.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Co-Authored-By: Olivier Tassinari <olivier.tassinari@gmail.com>
Just want to say that we should probably use |
I agree, it's not ideal, did you try to convince them otherwise? |
Well the issue got shut down immediately with the usual panicky response: Two versions (out of a thousand) broke SemVer contracts so we don't use SemVer anymore. Pretty curious attitude. Wonder if they deal with all bugs like this: If it breaks once we'll never use it again. |
Yeah, it's a hard tradeoff to make. It would be simpler for them if they had fewer dependencies. They have x10 more than us 🙃: |
Please describe charts and include a before state. These posts are nothing but inflammatory. Let's keep our cool here. |
No need to worry. We will find a solution, working on generating the chart, before it :). |
The redirection stats on Next.js v8 are not much better. The pages are also full of redirections. I have found the beginning of an answer. I will soon submit a pull request to get closer to a 100% crawling score. My plan:
|
Upgrades
next
to9.0.2
.The new build output allows tracking of each page individually.