Closed Steffen911 closed 2 weeks ago
vercel[bot]
commented
2 weeks ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Updated (UTC) |
|---|---|---|---|
| langfuse-docs | ✅ Ready (Inspect) | Visit Preview | Sep 26, 2024 4:06pm |
github-actions[bot]
commented
2 weeks ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
The following page changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/docs/deployment/self-host |
21.53 KB |
386.25 KB | 110.36% (🟡 +0.14%) |
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
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.
marcklingen
commented
2 weeks ago I think continuously documenting these options makes sense. I’d suggest to merge them to a v3 branch though as this otherwise might be confusing, thereby we can also collaborate on preview and final docs for v3 and share with early adopters once we release the alpha version
Steffen911
commented
2 weeks ago @maxdeichmann You had an idea on the "V3 branch". Do you have a ticket to execute on it? Otherwise, I could also move this into a draft PR/label it V3 and we keep it sitting until it becomes relevant.
maxdeichmann
commented
2 weeks ago Yes, i would create a "hidden" page which we can send around. This way we do not have a V3 branch. I already see merge conflicts incoming.
langfuse.com/docs/v3 would be the path for it.
maxdeichmann
commented
2 weeks ago Yes, i would create a "hidden" page which we can send around. This way we do not have a V3 branch. I already see merge conflicts incoming.
langfuse.com/docs/v3 would be the path for it.
cc @Steffen911 and @marcklingen i just pushed my preferred change.
github-actions[bot]
commented
2 weeks ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
The following page was added to the bundle from the code in this PR:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/v3 |
5.2 KB |
369.93 KB | 105.69% |
github-actions[bot]
commented
2 weeks ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
The following page was added to the bundle from the code in this PR:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/docs/v3 |
5.2 KB |
369.93 KB | 105.70% |
Steffen911
commented
2 weeks ago Good to go from my side. @marcklingen Any concerns on the approach?
marcklingen
commented
2 weeks ago Sounds good to me, good approach. Let me quickly add noindex headers to this page before merging. I can merge once done
github-actions[bot]
commented
2 weeks ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
The following page was added to the bundle from the code in this PR:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/docs/deployment/v3 |
5.26 KB |
369.99 KB | 105.71% |
github-actions[bot]
commented
2 weeks ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
364.77 KB (🟡 +54 B) |
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
The following page was added to the bundle from the code in this PR:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/docs/deployment/v3 |
5.28 KB |
370.04 KB | 105.73% |
github-actions[bot]
commented
2 weeks ago This analysis was generated by the Next.js Bundle Analysis action. 🤖
| Page | Size (compressed) |
|---|---|
global |
364.77 KB (🟡 +54 B) |
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
The following page was added to the bundle from the code in this PR:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/docs/deployment/v3 |
5.28 KB |
370.05 KB | 105.73% |
@marcklingen Do you think it makes sense to document this functionality already? Will probably have little use for self-hosters right now, but will become mandatory for V3. So we could get this written down now, even though we expect no one to make use of it.