Wrong import attribute typed as any, but should be typed as string

[johann1301s]

🔎 Search Terms

According to the documentation at MDN for Import attributes, the attribute value ie. dataN is of typestring.

In my VSCode setup using Typescript 5.8.2, this is typed as any in my .ts file:

My tsconfig is as follows:

{
  "exclude": ["dist"],
  "compilerOptions": {
    "jsx": "react",
    "target": "ES2022",
    "module": "esnext",
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "moduleResolution": "node",
    "strict": true,
    "skipLibCheck": true,
    "noImplicitAny": true,
    "isolatedModules": false
  }
}

🕗 Version & Regression Information

• This changed between versions ______ and _______
• This changed in commit or PR _______
• This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
• I was unable to test this on prior versions because _______

⏯ Playground Link

No response

💻 Code

// Your code here

🙁 Actual behavior

Import attribute is typed as any instead of string.

🙂 Expected behavior

Import attribute should be typed as string.

Additional information about the issue

No response

[RyanCavanaugh]

It's a grammar error to write anything but a string literal there, so I'm not sure why anyone cares what the hover says

[johann1301s]

Hi Ryan,

I get that the parser enforces string literals, but I still think this matters. When it’s typed as any, it makes the feature feel a bit unfinished. It also means that developers who don’t know the spec won’t get any hint that this is supposed to be a string.

For me, TypeScript has always been great at not just preventing errors, but also guiding you towards correct usage. That’s why this feels a bit off — and honestly makes me a bit hesitant to even use the feature.

It also seems like a pretty low-hanging fruit to improve the experience.

Thanks for considering it.

[johann1301s]

I would also like to add that, if it indicates that any value can be set, i.e 2, {...}, it seems odd that the parser then fails afterwords?

Normally if a property is of type any, the parser does not give error.

So essentially it is a conflict in what is being communicated?