🐛 BUG: Images assets imported in tsx files have the wrong type. about language-tools HOT 2 CLOSED

After some investigating I found that commenting out this line fixes the issue.

This really just confirms that the ts-plugin is to blame. I am not sure if this is an issue in volar.js or in astro language tools.
I would like to setup a minimum viable volar.js typescript plugin to confirm if it is in upstream but I can't really find any docs on this function:

import { createLanguageServicePlugin } from '@volar/typescript/lib/quickstart/createLanguageServicePlugin.js';

All the volar.js docs I have found do not include the ts-plugin piece.

from language-tools.

And another bit of information I found really strange.

Looking at this line in the example.tsx file:

import blogHeaderImg from "../assets/blog-header.jpg";

If I right-click on the "../assets/blog-header.jpg" both "Go to Definition" and "Go to Type Definition" is able to find the correct ImageMetadata type defined at node_modules/astro/client.d.ts

declare module '*.jpg' {
	const metadata: ImageMetadata;
	export default metadata;
}

However, if I right-click on the blogHeaderImg part, "Go to Definition" still takes me to the correct definition but "Go to Type Definition" shows the error:
No type definition found for 'blogHeaderImg'.

from language-tools.