Micha Reiser

That's something that should be figured out as part of the issue. I would favor a non parser specific option as we don't want that users must enable jsx in...

> Seem good candidates. > > For the name, no strong options. It can be the classic name or a new one. A `boolean` is probably not sufficient because Rome...

@ematipico Feel free to close this issue if you're already tracking this work in another issue.

Could I ask you to [vote for the preferred positioning of semicolons](https://github.com/rome/tools/discussions/3737) in the cases where the semicolon is required? It would help me to decide on the formatting that...

> Just wanted to say that it's been great to see how promptly and professionaly this was actioned ❤️ Thank you! I plan to push a pre-release tomorrow and would...

I've published a nightly Rome release (extension and CLI) a few minutes ago. Could you try the new version and report any semicolon-related issues (feel free to tag me)? ```bash...

Thanks for giving it a try! > Pre-release extension is super fast and no semicolons in sight. 🕺 > > With the CLI (which I don't really use), I get:...

> @sebmck rome init is not the correct command to do these kind of things. If you remember, we decided to remove such "import configuration from other tools" from init...

@dev-ardi are you able to reproduce this issue with the latest preview release?

> I'll take a look. We can split this task to: > > * [ ] imports/exports line break > > * [ ] JSX comment to props (specifically props...