Babel and TsConfig should be configured to use some aliasing system as opposed to rela

Implement aliasing and standardize imports about react-native-version-control HOT 1 OPEN

atomic71 commented on September 10, 2024

Implement aliasing and standardize imports

from react-native-version-control.

Comments (1)

gegeke commented on September 10, 2024

Adding the tsconfig (packages/tsconfig/base.json in this case, after this discussion) entries is pretty straightforward, for example

"compilerOptions": {
    "composite": false,
    "declaration": true,
    "declarationMap": true,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "inlineSources": false,
    "isolatedModules": true,
    "moduleResolution": "node",
    "noUnusedLocals": false,
    "noUnusedParameters": false,
    "preserveWatchOutput": true,
    "skipLibCheck": true,
    "strict": true,
-    "strictNullChecks": true
+    "strictNullChecks": true,
+    "baseUrl": ".",
+    "paths": {
+      "@web/*": ["../../apps/web/*"],
+      "@docs/*": ["../../apps/docs/*"]
+    }
  },

with this, everything seems to be OK:

Note:

You have to pnpm i, as the config files are moved to the node_modules with that command, and the dependencies are directed there.
gegeke/adding-ts-aliases branch is the suggestion (eslintrc.js is modified temporarily - rules should be turned back to error, when those ESLint issues are solved)

from react-native-version-control.

Recommend Projects