linkedin / linkedin/opticss

Code Splitting

Open
#39 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
713
Forks
23
PR merge metrics
No merged PRs in 30d

Description

Once OptiCSS runs on an analysis, the styles can be split by using subsets of the analysis to produce a base stylesheet for styles shared across code splits or styles that weren't enumerated as a part of a code split. Styles specific to each code split will be extracted to a split css file.

TBD: rewrite data may still be centralized, or it might be split-able as well.

Note: With declaration merging enabled, the benefits of code-splitting may not result in enough savings to warrant the extra complexity.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing how OptiCSS represents an analysis and its code-split subsets; the issue does not name files, tests, or an entry point. Done would mean producing a base stylesheet for shared or unassigned styles and separate CSS files for styles specific to each code split, with the rewrite-data question resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, typescript
Domain
build-system, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.