eslint-plugin-use-agnostic 0.9.10 → 0.10.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -76,7 +76,7 @@ With this list established, it thus becomes possible to recognize static import
|
|
|
76
76
|
|
|
77
77
|
Only the first line of code in a file is observed for the presence of a directive. If no top-of-the-file directive is present or recognized, the file is considered to not have a directive, defaulting to being understood as a Server Logics Module if it doesn't use a JSX file extension (`.js`, `.ts`) or as a Server Components Module if it does (`.jsx`, `.tsx`).
|
|
78
78
|
|
|
79
|
-
Aliased import paths are resolved only if your ESLint config file and your `tsconfig.json` file are in the same directory.
|
|
79
|
+
Aliased import paths are resolved only if your ESLint config file and your `tsconfig.json` file are in the same directory. At least to my knowledge, since the resolution depends on the `cwd` property from ESLint rules' `context` objects.
|
|
80
80
|
|
|
81
81
|
It is up to you to confirm that your Agnostic Modules are indeed agnostic, meaning that they have neither server- nor client-side code. `eslint-plugin-use-agnostic`, at least at this time, does not do this verification for you.
|
|
82
82
|
|
|
@@ -74,7 +74,7 @@ export const resolveImportPath = (currentDir, importPath, cwd) => {
|
|
|
74
74
|
// Case 3: Directory import (e.g., `./components` → `./components/index.ts`)
|
|
75
75
|
const indexPath = path.join(basePath, "index");
|
|
76
76
|
const directoryImportPath = findExistingPath(indexPath);
|
|
77
|
-
if (directoryImportPath) return
|
|
77
|
+
if (directoryImportPath) return directoryImportPath;
|
|
78
78
|
|
|
79
79
|
return null; // not found
|
|
80
80
|
};
|