-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Windows 10 backend loadPath #105
Comments
Hello, Your issue looks similar to the one I've encountered as well, #103. Until developers will fix the issue, you can use a workaround which worked for me. Define
|
My bad, thought that using Node's fileURLToPath would fix this. It'll be fixed on next release. |
+ update dependencies fixes #105
+ update dependencies fixes #105
# [1.0.0-beta.16](v1.0.0-beta.15...v1.0.0-beta.16) (2023-01-22) ### Bug Fixes * use unjs/pathe to resolve cross OS public path ([ad1d24f](ad1d24f)), closes [#105](#105)
🎉 This issue has been resolved in version 1.0.0-beta.16 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Alright, hopefully this should be fixed now. Thanks to @florian-lefebvre for mentioning https://github.com/unjs/pathe, super useful 👍 |
# [1.0.0-beta.16](yassinedoghri/astro-i18next@v1.0.0-beta.15...v1.0.0-beta.16) (2023-01-22) ### Bug Fixes * use unjs/pathe to resolve cross OS public path ([ad1d24f](yassinedoghri/astro-i18next@ad1d24f)), closes [#105](yassinedoghri/astro-i18next#105)
Describe the bug
version 1.0.0-beta.14
had
backend: {
loadPath: '/C:/Projects/OTHER/js/github-euxovv/public/locales/{{lng}}/{{ns}}.json', --- incorrect path
version 1.0.0-beta.15
backend: {
loadPath: 'C:ProjectsOTHERjsgithub-euxovvpubliclocales/{{lng}}/{{ns}}.json', -- incorrect pat
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Context (please complete the following information):
astro-i18next
version: [e.g. 1.0.0-beta.14,1.0.0-beta.15]astro
version: [e.g. 1.9.1]Add any other context about the problem here.
Possible fixes
version 1.0.0-beta.13 correct
The text was updated successfully, but these errors were encountered: