eslint-plugin-no-relative-import-paths
eslint-plugin-no-relative-import-paths copied to clipboard
MelvinVermeer
For ember projects, root dir is always `app`, but in app imports it's resolved from project name: Real dir: `app/services/login.ts` In-app alias: `my-application/services/login.ts` At the moment there is no way...
Hi! Thanks for the great plugin! My question is whether TS is supported?
We have the following configuration for this as per the readme, however in our Code Climate we are getting a warning on multiple files which don't have any imports. What...
Following #32, it looks like this plugin supports flat config. But how to use with flat config is not mentioned in the README.md. Would you be open to including that...
This plugin doesnt transform the following ```typescript export * from "./path" ``` to ```typescript export * from "@/path" ``` It would be nice if it did, because "export * from"...
## Add option to remove slash after '@' prefix in import paths ### **Description**: This pull request introduces a new configuration option for the `no-relative-import-paths` ESLint rule that allows users...
I see the errors when I just configure it as `"error"`, but when I add either `rootDir` or `allowSameFolder`, there are no errors even though there should be.
On imports not at the top level directory such as `import function from ".";` within `src/files/functions/` this rule does not see and correct them to `import function from "@files/functions"`
- Added replacement to handle double slashes at the start of generated paths when the prefix is a slash.
