reactjs
docs: updated HomeContent.js to German language.
HomeContent.js is now updated for German language. If you have suggestions for improvement, please let me know.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| de-legacy-reactjs-org | ⬜️ Ignored (Inspect) | Visit Preview | Mar 9, 2025 1:18pm |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
Size changes
📦 Next.js Bundle Analysis for react-dev
This analysis was generated by the Next.js Bundle Analysis action. 🤖
Five Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load |
|---|---|---|
/404 |
128.38 KB (🟡 +559 B) |
238.78 KB |
/500 |
128.39 KB (🟡 +559 B) |
238.79 KB |
/[[...markdownPath]] |
130.26 KB (🟡 +559 B) |
240.66 KB |
/errors |
128.66 KB (🟡 +559 B) |
239.06 KB |
/errors/[errorCode] |
128.64 KB (🟡 +559 B) |
239.04 KB |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
It looks good enough! After reading it again, I do believe "Mache Full-Stack mit einem Framework" and "Starte mit einem Framework" sound like very english-style german, but it is acceptable and the PR has been waiting for approval way too long!
My suggestion for the two markers I had, may be something like "Werde Full-Stack mit einem Framework" and "Beginne mit einem Framework", but it still doesn't sound good enough to my liking to add it as suggestion - hence I'll leave it as is and merge
Will this be merged soon? Try running the workflow again otherwise just close the PR.