0.38.8 broke absolute and aliased imports

[2-5]

Upgrade to 0.38.8 broke absolute and aliased imports. The code compiles and works fine, but shows errors in Volar:

tsconfig.json:

{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@/*": ["src/*"],
    }
  },

  "include": [
    "src/**/*.ts",
    "src/**/*.vue",
  ],
}

webpack.js:

const path = require("path")

module.exports = {
  resolve: {
    modules: ["node_modules", "src"],
    extensions: [".ts", ".js"],
    alias: {
      "@": path.resolve(__dirname, "src"),
    },
  },
}

[gitlilimin]

This problem also bothered me all day, you can try rollback to 0.38.5

i think this problem related to this commit

[johnsoncodehk]

I can't reproduce this problem, could your provide minimal reproduction?

[2-5]

Forgot to mention that I'm on Windows. I will see if I can make a repro repo.

…

On Sun, Jul 17, 2022, 20:21 Johnson Chu ***@***.***> wrote: I can't reproduce this problem, could your provide minimal reproduction? — Reply to this email directly, view it on GitHub <#1585 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4UOXSVLRPERIQCYHLZDKLVUQ6K5ANCNFSM53ZVPFHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[gitlilimin]

@johnsoncodehk i make a reproduction in #894

[DCLangX]

I have the same problem😭since volar updated today

[marty0678]

I'm not 100% if these two issues are related, but I'm getting similar TypeScript errors once I start editing a file since upgrading to 0.38.7 or 0.38.8 (these issues are not present on 0.38.6):

1. Open a file, everything is linted correctly, no errors, etc
2. Make a change, for example add const props = infront of defineProps

In the above example, you get the following result:

As you can see, the syntax highlighting is pretty odd indeed!

Another example of just odd behavior is take a component such as:

And add another simple component, and you see you get a TS error instantly, on the rest of the component that seems to have nothing to do with the change.

If you reload VsCode at this point, all the linting/errors for both issues go away, until you make another change.

I saw this issue was recent and was related to TypeScript issues, so if this should be a separate issue please let me know.

Thank you!

(I will revert to 0.38.6 for now as the issues do not happen there, I'm on Windows 11, VsCode 1.69.1, and using .vue and .js files (no typescript in my project specifically))

[Evertvdw]

Having the same issue as the post starter, I'm also on Windows, version 0.38.6 is the last version that works correctly for me.

[mmusket]

Also running same issue with latest version on windows

Just to add a datapoint
Problem happens for import links for .ts files inside of .vue files only

Example

File.vue 
import { xx} from '@/components/comp.vue' 
works ok

import { yy } from '@/store/store' 
throws ts(2307) 

Rolled back to 0.38.6

[tangerren]

in v0.38.8
i have the same problem

[chenjiangui]

me to

[lautr]

Having the same Problem with the following Setup

• Monorepo using pnpm
• 2 x Vue3 Projects
• Using Windows 10

Path aliases for one project work, for the other they don't.

Had the Issue with v0.38.8 & v0.38.7
Rolling back v0.38.6 seems to work.

[tajima738]

I am having the same issue.

• Windows 11
• v0.38.6 is fine
• We can build without problem
• Our Vue project files are in a subdirectory, opening the subdirectory directly in VSCode seems to work fine.

[szulcus]

I have the same problem

[2-5]

My Vue code (node_modules, src, tsconfig.json) is also in a subdirectory of the VC Code workspace like in the reproduction above. I set `typescript.tsdk` in `.vscode/settings.json` to make the extensions find it, maybe Volar now ignores this setting.

[johnsoncodehk]

@2-5 please open a new issue and provide repro case if still have this problem.