What is this?
Rome is a unified toolchain for JavaScript, TypeScript, and the web: one program that formats, lints, and bundles code, built to replace separate tools like Babel, ESLint, webpack, Prettier, and Jest.
Rome is a unified toolchain for JavaScript, TypeScript, and the web: one program that formats, lints, and bundles code, built to replace separate tools like Babel, ESLint, webpack, Prettier, and Jest.Is it a bunch of separate tools stitched together, or one program?One program. Rome unifies what used to live in separate tools, so formatting, linting, and bundling share a single base — one error display, parallel execution, caching, and one configuration.
One program. Rome unifies what used to live in separate tools, so formatting, linting, and bundling share a single base — one error display, parallel execution, caching, and one configuration.How do I get it running?Follow the Getting Started guide on the Rome homepage; the tool ships as an npm package, and a VSCode extension is available for editor integration.
Follow the Getting Started guide on the Rome homepage; the tool ships as an npm package, and a VSCode extension is available for editor integration.Do I need to install anything else before running it?Nothing extra: Rome is written in Rust, so it runs as a compiled binary; it is distributed as an npm package, with a VSCode extension on top.
Nothing extra: Rome is written in Rust, so it runs as a compiled binary; it is distributed as an npm package, with a VSCode extension on top.Is Rome still maintained?No. The original team stopped maintaining it, and the repository now points users to Biome, the community successor that receives new features and fixes.
No. The original team stopped maintaining it, and the repository now points users to Biome, the community successor that receives new features and fixes.Is it free to use, including commercially?Yes — MIT licensed, so free for any use; the project is also moderated under the Contributor Covenant Code of Conduct.
Yes — MIT licensed, so free for any use; the project is also moderated under the Contributor Covenant Code of Conduct.Why pick one unified tool over ESLint plus Prettier plus webpack?Because a shared base gives a cohesive experience: consistent error display across tools, parallelized work, caching, and a single configuration instead of several overlapping config files.
Because a shared base gives a cohesive experience: consistent error display across tools, parallelized work, caching, and a single configuration instead of several overlapping config files.What is Biome, and should I start there instead?Biome is the community-maintained successor to Rome; the Rome repo itself says Biome will provide the new features and fixes, so new projects should look at Biome first.
Biome is the community-maintained successor to Rome; the Rome repo itself says Biome will provide the new features and fixes, so new projects should look at Biome first.How much configuration does Rome need?Very little by design: Rome has strong conventions built in and aims to work with minimal configuration.
Very little by design: Rome has strong conventions built in and aims to work with minimal configuration.Which topics is it in?formatter, bundler, toolchain, linter, vscode-extension, code-quality, static-analysis, deprecated, css, html, markdown, web-development
formatter, bundler, toolchain, linter, vscode-extension, code-quality, static-analysis, deprecated, css, html, markdown, web-development