Build Performance and Scale Testing
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- performance, testing
Research direction
Start by reviewing the CSS Blocks build process and how CSS blocks are currently compiled. Define predictable, configurable scale-testing parameters and identify how build-time results should be recorded. Done means the system produces meaningful, repeatable performance numbers for CSS Blocks adopters.
Written by the indexing model from the issue text.
Description
We need a system for perf testing css blocks build time performance at scale with predictable and yet configurable parameters so that we can give meaningful numbers to people who are considering adopting CSS Blocks.
- Dominant language
- TypeScript
- Stars
- 6.3k
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No 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 linkedin/css-blocks
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
linkedin/css-blocks#592 ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
linkedin/css-blocks#590 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
linkedin/css-blocks#563 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 5/100
linkedin/css-blocks#562 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
linkedin/css-blocks#555 ·
All issues in linkedin/css-blocks
Similar issues
-
perf(core): getComments() runs the approved count and the comment list as two sequential queriesOpenarea/core bot:bug bot:working
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
emdash-cms/emdash#3905 · 2 comments ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 90/100
lingdojo/kana-dojo#31728 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
selective-claw: freshTailTurns=0 keeps ALL turns verbatim and summarizes none (slice(-0) === slice(0))Possibly taken @zjncs claimed this today. Opencomponent:tokenless
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
agentic-os-org/ANOLISA#6112 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
rjsf-team/react-jsonschema-form#5439 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day