Skip to content

[feat] Support jsconfig.json by default #335

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rakleed opened this issue Dec 20, 2024 · 4 comments · Fixed by #368
Closed

[feat] Support jsconfig.json by default #335

rakleed opened this issue Dec 20, 2024 · 4 comments · Fixed by #368

Comments

@rakleed
Copy link

rakleed commented Dec 20, 2024

It would be nice if you added support of jsconfig.json without additional configuration of project.

See for example: 9romise/eslint-import-resolver-oxc#46

@SukkaW
Copy link
Collaborator

SukkaW commented Dec 21, 2024

This should be easily doable by modifying the parameters passed to get-tsconfig.

@JounQin
Copy link
Collaborator

JounQin commented Mar 10, 2025

Doesn't it? See #161

Of cause, the document should be updated.

Duplicate of ##334

@JounQin JounQin closed this as completed Mar 10, 2025
@rakleed
Copy link
Author

rakleed commented Mar 10, 2025

Doesn't it? See #161

@JounQin now you need to specify the project property and the path to the jsconfig.json file. I'm talking about making this unnecessary so that you automatically find this file.

At least in my case, the jsconfig.json file located at the root of the project was not automatically found, and absolute paths in imports were not resolved correctly. See https://stackblitz.com/edit/vitejs-vite-o1lrg1rf?file=eslint.config.js

@JounQin
Copy link
Collaborator

JounQin commented Mar 12, 2025

See #368, in next major tsconfig.json/jsconfig.json will be resolved by default if not provided.

And you can try it out today.

#368 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants