Set up i18n package

[araujogui]

Description

Set up i18n package

Validation

ESLint is throwing Unable to resolve path to module '@node-core/website-i18n' error and I couldn't figure out the fix. Some help is welcome

Related Issues

Related to #5405

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run npm run format to ensure the code follows the style guide.
• I have run npm run test to check if all tests are passing.
• I have run npx turbo build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Sep 13, 2024 1:04pm

[github-actions]

Note

Your Pull Request seems to be updating Translations of the Node.js Website.

Whilst we appreciate your intent; Any Translation update should be done through our Crowdin Project.
We recommend giving a read on our Translation Guidelines.

Thank you!

[bmuenzenmeyer]

will take a look at this as i can - also #6993 might conflict

[bmuenzenmeyer]

I can recreate
I've tried adding "dependsOn": ["@node-core/website-i18n#build"], according to https://turbo.build/repo/docs/crafting-your-repository/configuring-tasks#depending-on-a-specific-task-in-a-specific-package - but no luck yet

[ovflowd]

I can recreate I've tried adding "dependsOn": ["@node-core/website-i18n#build"], according to turbo.build/repo/docs/crafting-your-repository/configuring-tasks#depending-on-a-specific-task-in-a-specific-package - but no luck yet

Can we ask help for to our in-house Turborepo specialist on Slack?

[bmuenzenmeyer]

@anthonyshew curious if you'd have some time to look at this and help out? the lint step is failing on the branch

[anthonyshew]

This is going to end up being a misconfiguration somewhere on ESLint or typescript-eslint, but it's going to be a fun time trying to figure out where it is. 😄 That's at least my early hypothesis since the application appears to be building correctly, so module resolution is doing what it's supposed to.

Digging in...

[anthonyshew]

After I couldn't sort it out, I asked Josh for his help. In typical Josh fashion, he overdelivered.

[ovflowd]

I've rebased the PR, hopefully this is fixed now!

[ovflowd]

cc @JoshuaKGoldberg, it seems like tests are failing due to being unable to import the module; I assume it's because Jest is not using TypeScript's module resolution here. (note that our website uses a mix of TypeScript and plain ESM, So ESM should also be able to resolve said modules)

My assumption here is that the Jest config needs to be updated to understand the module resolution for the said module. (Just a 5 minute guess, after looking on the CI logs)

[ovflowd]

There are many issues here regarding module resolution during tests and build. This definitely needs to be addressed.

[ovflowd]

To be honest, the ESlint v8 setup is really flaky, we are using some weird canary versions of plugins, and I'm really uncomfortably with how things are 🫠

This added a hella of instability here.