-
# Problem
When configuring `tsconfig.json` with `paths`:
```
{
"compilerOptions": {
"baseUrl": "./",
"paths": [
"@fancyModules/*": ["./src/modules/fancyModule/*"]
]
…
-
I've reduced the test case to this: https://stackblitz.com/edit/vitest-dev-vitest-oip9io?initialPath=__vitest__/
You can see that this Vite plugin fails entirely to resolve paths using TSConfig set…
-
Most frontend project use tsconfig paths. And import scss like this `@import '@/style/theme';`.
```json
// tsconfig.json
{
"compilerOptions": {
"paths": {
"@/*": ["./sr…
-
When trying to import a client component using typescript path alias, I get the following error on screen
```
TypeError: Failed to fetch dynamically imported module: http://localhost:3002/src/compon…
-
### Current Behavior
tsconfig.json file:
`
{
"compilerOptions": {
"paths": {
"@app/themes/*": ["libs/themes/src/muiThemes/*"]
}
},
}
`
it resolves in rspack config…
-
Since typescript 5.5, it is possible to use the ${configDir} variable inside `include`/`exclude` clauses to reference the directory path where the current tsconfig is located, but unfortunately vite-t…
-
### Environment
Node version: 22.5.1
npm version: 10.2.5
ESLint version: 9.7.0
eslint-plugin-n version: 17.9.0
Operating System: Windows 11
### What rule do you want to report?
n/no-missing-i…
-
### Describe the bug
(1) Svelte components imports that use absolute paths, create a `cannot find module or its corresponding type declarations ts(2307)` error in VS Code. Relative path imports work …
-
### Current Behavior
Nx is unable to resolve the baseUrl for a library inside thhe NxTsconfigPathsWebpackPlugin although baseUrl exists in tsconfig.base.json and we have extended that file all the…
-
### Use case description
A change to load [tsconfig-paths](https://www.npmjs.com/package/tsconfig-paths) in supoort of serverless.ts definition files and secondly to optionally …