Skip to content
This repository was archived by the owner on Aug 31, 2023. It is now read-only.

rome/tools

Folders and files

NameName
Last commit message
Last commit date
Jul 28, 2022
Aug 2, 2022
May 4, 2021
Aug 1, 2022
Jul 27, 2022
Jul 21, 2022
Nov 17, 2021
Jul 30, 2022
Jul 29, 2022
Feb 4, 2022
Jan 16, 2022
Aug 2, 2022
Jun 20, 2022
Feb 26, 2022
Jul 14, 2022
Jul 5, 2022
Oct 14, 2021
Jul 22, 2022
Jul 29, 2022
Jun 17, 2022
Sep 17, 2021
Jul 12, 2022
Jul 1, 2022
May 11, 2022

Repository files navigation

Rome's logo depicting an ancient Roman arch with the word Rome to its side Rome's logo depicting an ancient Roman arch with the word Rome to its side

MIT licensed Discord chat CI on main npm version VSCode version

Rome is a formatter, linter, bundler, and more for JavaScript, TypeScript, JSON, HTML, Markdown, and CSS.

Rome is designed to replace Babel, ESLint, webpack, Prettier, Jest, and others.

Rome unifies functionality that has previously been separate tools. Building upon a shared base allows us to provide a cohesive experience for processing code, displaying errors, parallelizing work, caching, and configuration.

Rome has strong conventions and aims to have minimal configuration. Read more about our project philosophy.

Rome is written in Rust.

Rome has first-class IDE support, with a sophisticated parser that represents the source text in full fidelity and top-notch error recovery.

Rome is MIT licensed and moderated under the Contributor Covenant Code of Conduct.

Installation

npm i rome@next

Usage

Format files:

rome format --write ./path ./path/to/file.js

For complete documentation, please visit the official website.

Philosophy

The project philosophy can be found on our website.

Community

Contribution and development instructions can be found in CONTRIBUTING.

Additional project coordination and real-time discussion happens on our Discord server. Remember that all activity on the Discord server is still moderated and will be strictly enforced under the project's Code of Conduct.

Technical documentation

If you're curious to know our internals, you can browse our technical documentation.