fix(docs-i18n-tracker): update translations import

[HiDeoo]

What kind of changes does this PR include?

• Something else!

Description

This PR fixes an issue with the Starlight Docs Translation Status. Following the changes in #1003, it now errors with the following:

Error [ERR_UNSUPPORTED_DIR_IMPORT]: Directory import 'starlight/packages/starlight/translations' is not supported resolving ES modules imported from starlight/packages/starlight/utils/createTranslationSystem.ts

Note: I got this error locally after noticing that the tracker was not updating, I have no idea where to check the logs for the production one.

This is due to the Node import specifiers spec:

Directory indexes (e.g. './startup/index.js') must also be fully specified.

And tsm not handling this case specifically.

This PR specifies the index file in the import statement, which fixes the issue.

Another approach to avoid the change could be:

• Add "type": "module" to docs-i18n-tracker/package.json
• Replace tsm by tsx which handles this case

[changeset-bot]

🦋 Changeset detected

Latest commit: f21476a

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

This PR includes changesets to release 1 package

Name	Type
@astrojs/starlight	Patch

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

[netlify]

✅ Deploy Preview for astro-starlight ready!

Name	Link
🔨 Latest commit	f21476a
🔍 Latest deploy log	https://app.netlify.com/sites/astro-starlight/deploys/6543c081aaf9890008277447
😎 Deploy Preview	https://deploy-preview-1025--astro-starlight.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 92 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[delucis]

Note: I got this error locally after noticing that the tracker was not updating, I have no idea where to check the logs for the production one.

The deployment logs are on Netlify and I can confirm they match your local error — good catch! I think you should be able to see them, although not easily find them. Here’s a recent run: https://app.netlify.com/sites/starlight-i18n-dashboard/deploys/6543a2ce75e62e000845952e

This change looks good to me. I guess hypothetically this could impact Starlight users, so we should probably add a patch changeset to release this fix?

[HiDeoo]

I think you should be able to see them, although not easily find them.

Ah thanks, I can indeed see them.

I guess hypothetically this could impact Starlight users, so we should probably add a patch changeset to release this fix?

Yeah, thought about that, but was not sure what to say or what the scenario could be (that's also why I included an alternative without the change ^^). I just pushed one with "Internal: fix import issue in translation string loading mechanism" but feel free to change it if you have a better idea.

Note: I am also not sure if merging this is enough to trigger a rebuild?

[delucis]

Thanks for adding the changeset — I think this will do!

Note: I am also not sure if merging this is enough to trigger a rebuild?

Yeah, we very aggressively rebuild that site to keep it up to date by hitting the rebuild webhook for each pull_request event on GitHub (only really need to do it when PRs are opened but GitHub’s webhook UI only supports triggering for all PR events) as well as for commits to main.