Static analysis
- Dominant language
- JavaScript
- Stars
- 284
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Throwing this out here for discussion.
RCSS is an experiment (one that seems to work fine on a small scale at least). There are already plenty of other asset bundling/loading solutions that use static analysis. Currently I have no plan in introducing some here, partially because I want less overlap and partially because it gets harder to maintain and is one extra compilation step.
I'll see how far I can piggy ride on whatever existing `require` solution (browserify, webpack). Maybe I'll consider static analysis in the future.
Contributor guide
No contributing guide indexed for this repository
Research direction
This issue is a discussion about possibly adding static analysis to RCSS, with no implementation files, tests, entry point, or concrete acceptance criteria named. Start by reviewing the existing require integration and how browserify or webpack are currently used; work is not defined as done until the project specifies whether static analysis should be supported and what behavior it must provide.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100