Comment

Paolo Božac

I had pretty much the same hurdles when trying out Rome recently. My two cents about the "Things that didn't work so well
"
1) Lint, check, or format?
There is no `lint` command. Here is a mapping:
format => rome format <INPUTS...>
lint => rome check <INPUTS...>
lint:fix => rome check <INPUTS...> --apply-suggested

2) How do I specify wildcards?
This one is something I struggled with, and even though on the docs it stands "A list of Unix shell style patterns." When I tried to define my glob pattern based on this (https://globster.xyz/) it didn't work as expected. So I ended up with defining "rome check ./packages/react-**/" to target all the files inside `/packages/react-icons` and `/packages/react-components` folders with the following config for defining ignore patter inside rome.json: Docs (https://docs.rome.tools/configuration/#filesignore)
```
"files": {
"ignore": [
"*/node_modules/**",
"*/dist/**",
"./packages/docs/**",
]
}
```
https://docs.rome.tools/configuration/#filesignore

3) There's no documentation about how to ignore certain rules
Probably there wasn't docs written about it at the time of writing this post, but for newcomers - here is a link to the docs section about it: https://docs.rome.tools/linter/#ignoring-code

4) The rome.json file is JSON
Exactly. I also wanted to to the same but unfortunately I needed to put comments somewhere else (README.md or similar)

And one more thing, apart from the speed gain, the biggest impact of using rome is that I replaced 15 dependecies (eslint, prettier and its plugins/configs) with just one :)