Re:Rome: A Linter for JavaScript and TypeScript
by sebastianmck on Saturday August 08, 2020 @08:25PM
(#24096348)
It's a linter so you don't need to ask any of those questions. Future usage as a bundler isn't dependent on any decision to use it as a linter.
Re:Rome: A Linter for JavaScript and TypeScript
by wildpeaks on Sunday August 09, 2020 @06:45AM
(#24098688)
It does matter if the only value of the linter at the moment is that it will be part of a set of tools to replace the entire toolchain.
It already took forever for the ecosystem to get JSHint, Tslint and others to converge into Eslint.
- does it handle images imports
- does it handle scss imports
- if not, does it require css-in-js (and if so which one)
- does it handle shaders imports (and other arbitrary dependencies that need custom processing to get embedded in the bundle)
- does it generate SRI hashes for stylesheets and scripts
- can it generate web workers
- can it generate node bundles or only browser bundles
- can it split chunks
- do you still get TS intellisense in VSCode
- can it be used with Rust and/or Webassembly