🐛 Rome check: Cannot find ts files imported as js files

[Conaclos]

What happened?

1. create two files a.ts and b.ts in the same folder
2. import b.ts as a js file in b.ts
3. run rome linter rome check.

Rome check outputs Cannot find ./a.js from b.ts

@filename a.ts
export function f(){}

@filename b.ts
import {f} from "./a.js"

Expected result

Rome should identify js imports as ts imports if the js file does not exist.

The use of js extensions in imports is supported by TypeScript and enables direct execution of esm files in modern versions of nodejs.

Rome version

10.0.0

Configuration file of your project

name: "xxx"
root: true

Code of Conduct

• I agree to follow Rome's Code of Conduct

[ematipico]

Is it actually a bug? I'd say it's a feature request. Rome doesn't fully support ESM at the moment so I think it's expected as behaviour.

[Conaclos]

@ematipico
This makes sense. Should I close this issue and open a new one?

Is there any way to suppress a lint rule for an entire project? According to the docs a rule can be disabled for a given file.

[ematipico]

Rome diagnostic (not a lint rule) should show you the type of error you're getting, called category.

Then add a suppression

If you're not happy with the result, you could use the latest nightly where we disabled this kind of errors.

About the issue, yes it would make sense to close it. About the feature, usually we tend to use a discussion to talk about it then open an actionable issue once the requirements are solid.