sebmck
Follow
Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 50 million developers.
Sign up
Pinned
1,643 contributions in the last year
Contribution activity
August 2020
Created a pull request in romefrontend/rome that received 3 comments
Path and various fixes
Summary It's easier for me to create a single PR so I can batch up a lot of these fixes since they're fairly simple and I have limited time to wor…
+475
−349
•
3
comments
- Final batch of release fixes
- More release tweaks
- More batched release fixes
- Misc release fixes
- Fix and add tests for fix decisions - fixes #932
- Blog post tweaks
- Add test for `rome init` in a directory with an existing rome project - fixes #801
- Fix Client#generateRageSummary - fixes #931
- [website] Add blog post
- Website accessibility tweaks
- Change website tagline, add more CLI screenshots and docs
- Code quality polish
- Remove Position.index
- Even more documentation
- Improve error handling
- Fix silent request query property
- Fix comment insertion and suppressions
- Add state to compiler visitors, add optimizations for memory file system and parsing
Created an issue in romefrontend/rome that received 3 comments
📎 Lower supported Node version
VS Code ships with an older version of Node that we only noticed yesterday does not support recursive on rmdir. We can lower it again once that has…
3
comments
- 📎 Cascading dying worker
- 📎 Improve test performance and stability
- 📎 Remove PATH from rage —summary
- ☂️ Markdown support
- ☂️ CSS support
- ☂️ HTML support
- 📎 Unquote valid JS identifier property keys and computed members
- 📎 Considering removing `hr` from console output
- 📎 Binary bridge format
- 📎 Warn if there are multiple configs
- 📎 Enable `--changed` for `check` by default in `rome ci`
- 📎 Slim down huge internal files
- 📎 Additional lint rules from IntelliJ
- 📎 Detect `debugger` statements in bundler and enable it while running tests
- 📎 Interactive yes/no when suggesting CLI commands in a TTY
- 📎 Always retain `@jsx` header even if the leadingComment node it's attached to is removed
- 💭 Consider mandatory lint suppression explanations
- 📎 Fatal error coloring sometimes has unhighlighted trailing characters
- ☂️ Future performance optimizations
- 📎 Import ESLint rule tests
- 📎 Split JS regex lint rules into a separate category
- 📎 Add fixable tag to lint rule docs
- 📎 Support `/* global */` comments for declaring globals