cubanducko / playwright-i18next-fixture Goto Github PK

Hi,
Great plugin there, thanks! I've used it for only one language at first, so I set lng directly and it's working fine!!
But now I want to add a new language (add tests to the same website, but with a different locale / language), and I can't make it work..
Can you help? Did you have to manage this use case?

Thanks!

What is the current behavior?
I remove the lng key in options and I added:
plugins: [LanguageDetector] with import LanguageDetector from 'i18next-browser-languagedetector';

And now, it can't find the right language of the website (I use a locale on playwright project, and on the website, the html tag as a lang attribute)

Debug mode tells me:

i18next::languageUtils: rejecting language code not found in supportedLngs: dev
i18next::languageUtils: rejecting language code not found in supportedLngs: dev
i18next: languageChanged dev
i18next: initialized {
  debug: true,
  [...]

Steps to reproduce it and if possible a minimal demo of the problem. Paste the link to your JSFiddle or CodeSandbox example below:

What is the expected behavior?
I expect to have the correct translations of the website under test
A little about versions:

• OS: MacOS
• Browser (vendor and version): Firefox
• React:
• react-use:
• Did this worked in the previous package version?

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀