Wrong import path for types.d.ts ContentConfig

[loucyx]

Astro Info

Astro                    v4.1.2
Node                     v21.5.0
System                   macOS (arm64)
Package Manager          pnpm
Output                   static
Adapter                  @astrojs/vercel
Integrations             @astrojs/sitemap
                         @astrojs/tailwind
                         astro-expressive-code

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

The types generated from packages/astro/src/content/types-generator.ts generate a ContentConfig type that looks like this:

type ContentConfig = typeof import("../src/content/config");

The issue with it is that if our tsconfig.json has verbatimModuleSyntax set to true, that import is invalid because it doesn't have the file extension, so we end up with any instead of the strong type we wanted. If instead, that import was written like this:

type ContentConfig = typeof import("../src/content/config.js");

Then it would work in all cases.

What's the expected result?

Get the proper type for my content, right now I'm getting any for it.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/verbatim-module-issue?file=src%2Fpages%2Frss.xml.js

Participation

• I am willing to submit a pull request for this issue.

[loucyx]

I would create a PR directly for packages/astro/src/content/types-generator.ts:468 but I wanted to check with you folks to see how you prefer to solve this issue, because adding a .js on that string would fix it, but maybe you have an util for that already.

[bluwy]

Adding .js seems harmless to me and should work in all TS versions. Feel free to contribute the fix!