fix: add support for js/mjs file extensions for Content Collections config file

[MoustaphaDev]

Changes

Closes #6179

Testing

Check that an error is thrown when the frontmatter doesn't match the schema of the collection defined in the config.mjs file.

I could add a test case for a config.js but it seems redundant as the config file has to be a module anyway.

Docs

Bug fix, we already document this

[changeset-bot]

🦋 Changeset detected

Latest commit: 08d0902

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[MoustaphaDev]

Patch because this is already documented

[bholmesdev]

This code looks great! However, there's a caveat to using mjs configs: intellisense will not work unless "allowJs: true is present in your tsconfig.json, or if you switch to a jsconfig.json.

I'm curious if we can check for allowJs in your tsconfig, and log a warning if it isn't present. This would guide users in the right direction to avoid future support tickets. A callout in our docs would be great too!

[MoustaphaDev]

Ah thanks for the heads-up! I just found this commit on discord withastro/docs@bb99ae0 where allowJs was removed from the tsconfig.json because it would break the astro:content virtual module. Did you find a way to get around the side effects of allowJs?

[bholmesdev]

@MoustaphaDev Ah good catch. I've been unable to replicate that issue outside of docs but it's probably worth more testing. I verified astro:content works as expected using allowJs in the blog starter on my end. Mind trying on your end as a sanity check?

[MoustaphaDev]

I don't see anything breaking @bholmesdev! Working on implementing the warnings
I'll open a PR in docs too

[bholmesdev]

Super small nit but looks amazing! Feeling configdent 👏

[tschaub]

Thanks for the work on this, @MoustaphaDev!