-
It looks like TypeScript compiler resolves files relative to the location of the `tsconfig.json` file (however, I couldn't find anything about paths resolution in the official documentation).
Is th…
-
Type: Bug
VS Code project set up:
nvm, node.js (V^18), npm, typescript (V^5), webpack-dev-server (V^5)+ html-webpack-plugin(V^5).
After loading VS Code, in a few minutes, I get the notification t…
-
tsc-alias is not resolving aliased root directory defined in tsconfig.json paths parameter. I tried different versions of typescript and tsc-alias and it didn't work.
tsconfig.json :
```json
{…
dvqc updated
2 months ago
-
I'm trying to use Pulse (migrated from Agenda). This is my code
```
import Pulse from '@pulsecron/pulse';
const mongoConnectionString = process.env.MONGO_URL || "mongodb://127.0.0.1:27018/pulse…
-
I ran into an issue where the advice in the docs for using typescript with v1 of the library made my absolute imports throw errors.
I got around it by using the "paths" key in my "compilerOptions" …
-
### What problem does this feature solve?
Currently, cli-plugin-typescript creates `tsconfig.json` with aliases setup that repeats vue-cli's webpack aliases, namely:
```
"baseUrl": ".",
…
-
### Describe the bug
Have error when use it in my code.
![image](https://github.com/toonvanstrijp/nestjs-i18n/assets/78104957/98e792a9-f5dd-4868-a9a2-671a59fcc4f9)
![image](https://github.co…
-
### 🔍 Search Terms
"extends", "merge", "compilerOptions", "paths", "outdir", "include", "exclude", "typeRoots", "tsconfig", "ability to merge tsconfig"
### ✅ Viability Checklist
- [X] This wo…
-
I am encountering an issue while trying to import SVG files as React components in my Vite + React + TypeScript project. Despite following the documentation and proper configuration, I receive the fol…
-
**`Severity Threshold: 🔵 MEDIUM`**
# 7 Potential vulnerability sources found within this repo
| `🔴 CRITICAL` | `🟡 HIGH` | `🔵 MEDIUM` | `⚪ LOW` |
|-|-|-|-|
| 0 | 1 | 6 | 0 |
**`ID: 01J2FGEXB46YP4VH…