eslint-plugin-use-agnostic 0.9.8 → 0.9.10
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 +0 -14
- package/library/_commons/utilities/helpers.js +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -42,20 +42,6 @@ export default defineConfig([
|
|
|
42
42
|
]);
|
|
43
43
|
```
|
|
44
44
|
|
|
45
|
-
And don't forget the VS Code settings via `./.vscode/settings.json`:
|
|
46
|
-
|
|
47
|
-
```json
|
|
48
|
-
{
|
|
49
|
-
"eslint.useFlatConfig": true,
|
|
50
|
-
"eslint.validate": [
|
|
51
|
-
"javascript",
|
|
52
|
-
"javascriptreact",
|
|
53
|
-
"typescript",
|
|
54
|
-
"typescriptreact"
|
|
55
|
-
]
|
|
56
|
-
}
|
|
57
|
-
```
|
|
58
|
-
|
|
59
45
|
## How it works
|
|
60
46
|
|
|
61
47
|
In the beginning, there were not two kinds of modules in the Fullstack React Architecture (server vs. client). There were three:
|
|
@@ -46,7 +46,7 @@ const findExistingPath = (basePath) => {
|
|
|
46
46
|
* @returns The absolute resolved path or `null` if no path is found.
|
|
47
47
|
*/
|
|
48
48
|
export const resolveImportPath = (currentDir, importPath, cwd) => {
|
|
49
|
-
//
|
|
49
|
+
// Step 1: Resolve baseUrl and aliases (if tsconfig.json `paths` exists)
|
|
50
50
|
const config = loadConfig(cwd);
|
|
51
51
|
|
|
52
52
|
const resolveTSConfig =
|
|
@@ -58,7 +58,7 @@ export const resolveImportPath = (currentDir, importPath, cwd) => {
|
|
|
58
58
|
? resolveTSConfig(importPath, undefined, undefined, EXTENSIONS)
|
|
59
59
|
: null;
|
|
60
60
|
|
|
61
|
-
//
|
|
61
|
+
// Step 2: Resolve relative/absolute paths
|
|
62
62
|
const basePath = aliasedPath || path.resolve(currentDir, importPath);
|
|
63
63
|
|
|
64
64
|
// does not resolve on node_modules
|