element: the first-load size budget is used up
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, web-dev
- Domain
- frontend, performance
Research direction
Read build.js and inspect the first-load size report from npm run size -w pivotkit-element; compare the local result with the CI measurement described in the issue. Identify code that can load on demand and assess how the 175 KiB budget should be enforced. Done means the first-load budget policy and the local-to-CI size check are addressed.
Written by the indexing model from the issue text.
Description
pivotkit-element's first load ("initial" in build.js SIZE_BUDGET_KIB) is at its budget. On main, CI measured 175.0 KiB gzip against 175 KiB, and #545 raised the budget to 175.1 KiB for 40 bytes of shared grid constants. Each new feature that touches the first load will hit the budget again.
CI measures about 0.6 KiB more than a local macOS build, so a local npm run size -w pivotkit-element can pass while CI fails.
Proposal:
- Find what in the first load could load later: chart planning code, menus that open only on demand, texts of rare messages.
- Decide whether the budget stays a hard line at 175 KiB, or moves with a recorded reason.
- Make the local size check match CI, for example by pinning the same esbuild and gzip level, or by printing the CI difference.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 250
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from eizedev/pivotkit
-
accessibility area:react bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area:tests
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area:cli bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
area:cli enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:react enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in eizedev/pivotkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
embedpdf/embed-pdf-viewer#1116 ·
Maintainers usually reply within 1 day
-
[Docs]: Clarify theme variables location and usage in CONTRIBUTING.mdPossibly taken @srishtimishra520-beep claimed this today. Openkind/docs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
meshery/meshery.io#3220 · 1 comment ·
Maintainers usually reply within 1 day
-
Module: Analytics P2 Team S Type: Infrastructure
Difficulty 1/5 Under an hour Newbie friendliness 90/100
google/site-kit-wp#14190 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
maathimself/mailflow#801 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
falbany/ProFiles#187 · 1 comment ·
Maintainers usually reply within 1 day