ChristianMurphy / ChristianMurphy/linter-selective
Reduce startup impact
Open
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
currently linter-selective is adding ~900ms to Atom startup time.
It looks like `linter-markdown` is working around this by delaying package loading until activation.
https://github.com/AtomLinter/linter-markdown/blob/b79bbdb69a281b0c4f080c0bece8e2029a9f6c3c/lib/index.js#L32-L51
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked linter-markdown lib/index.js lines 32-51, then locate the corresponding package-loading entry point in linter-selective. Done means reducing the reported ~900ms Atom startup impact while preserving the package's existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100