Closed daoxincc closed 2 years ago
@daoxincc module path is an absolute path composed of CMD and target path,This is correct
@daoxincc However, please do not let the path appear in Chinese, which may be illegal
@daoxincc Finally, you should ensure that auto imports.d.ts
is scanned to ts
why it's not a relative path with project dir?
it's my tsconfig.json
{
"compilerOptions": {
"target": "esnext",
"useDefineForClassFields": true,
"module": "esnext",
"moduleResolution": "node",
"strict": true,
"jsx": "preserve",
"sourceMap": true,
"resolveJsonModule": true,
"isolatedModules": true,
"esModuleInterop": true,
"types": ["vite/client"],
"baseUrl": ".",
"paths":{
"@": ["src"],
"@/*": ["src/*"]
},
"lib": ["esnext", "dom"],
"allowJs": true
},
"include": ["src/**/*.ts", "src/**/*.d.ts", "src/**/*.tsx", "src/**/*.vue"],
"references": [{ "path": "./tsconfig.node.json" }],
"exclude": ["node_modules", "dist"]
}
@daoxincc Because the absolute path does not need more configuration, you can get friendly prompts,This will be more user-friendly
thanks for u comment . but I cant use component tag link in vue template(vscode / webstorm). how can i fix it.
@daoxincc I don't think this is the problem caused by the resolver. Maybe you can go to volar/issues to issue
It's my auto-imports.d.ts, I dont know why
package.json
vite.config.ts
auto-imports.d.ts