Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

volar doesn't read `compilerOptions.types` of tsconfig.json

See original GitHub issue

volar version: v0.39.2 vscode version: 1.69.2

repo: https://github.com/aimergenge/blog

see this file: src/pages/index.vue:2

.png module type is in vite/client and tsconfig.json’s compilerOptions.types includes it

Issue Analytics

State:
Created a year ago
Reactions:4
Comments:12 (1 by maintainers)

Top GitHub Comments

1reaction

fliebe92commented, Aug 2, 2022

v0.39.1 works fine for me, afterwards, it’s broken.

0reactions

johnsoncodehkcommented, Sep 21, 2022

@zhouxiang1991 If still not working in v0.40.13 or later, please open an issue and provide repro case.

Top Results From Across the Web

Why does VSCode not pick up path aliases in tsconfig?

In my case, the aliases can not be read by vs code on Jest ... The solution is add a settings.json in .vscode...

TSConfig Reference - Docs on every TSConfig option

Intro to the TSConfig Reference A TSConfig file in a directory indicates that the directory is the root of a TypeScript or JavaScript...

How to Fix the TypeScript Intellisense Template Error in Vue

I recently got this error while working on a Vue 3 project: TypeScript intellisense is disabled on template. No need to panic, just...

Using Vue with TypeScript - Vue.js

When configuring tsconfig.json manually, some notable options include: compilerOptions.isolatedModules is set to true because Vite uses esbuild for transpiling ...

cannot find module' or its corresponding type declarations vue

This is because TypeScript does not resolve webpack aliases automatically. For TS to resolve aliases, they should be added in tsconfig.json under ...