feat(vite-plugin): Add strict option to vite plugin

[hahn-kev]

Description

Adds a new config option to the vite plugin to allow passing strict: true to the compile step. We'd like to have CI builds fail if there's missing translations but this option was hard coded.

Example:

const config: UserConfig = {
  plugins: [lingui({strict: true})],
};

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Examples update

Checklist

• I have read the CONTRIBUTING and CODE_OF_CONDUCT docs
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation (if appropriate)

Note

I added a test, however these tests don't run on windows so I'm not able to run the test on my machine.
There's no docs for the vite plugin config so I'm not sure where this new option should be documented.

I recognize that there's not an issue for this, however this is such a minor change I figured I'd just do it rather than making an issue ahead of time.

[vercel]

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

Name	Status	Preview	Updated (UTC)
js-lingui	✅ Ready (Inspect)	Visit Preview	Mar 11, 2025 11:04am

[github-actions]

size-limit report 📦

Path	Size
packages/core/dist/index.mjs	2.91 KB (0%)
packages/detect-locale/dist/index.mjs	618 B (0%)
packages/react/dist/index.mjs	1.35 KB (0%)

[hahn-kev]

Hum, I'm not sure what's going on, I don't know enough about how lingui works to write a good test for strict mode, does anyone have a suggestion?

[timofei-iatsenko]

Thanks for the contribution, i'll take it from there. Sorry for the late response.

[timofei-iatsenko]

Continue here #2198