-
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
autodetection build error #15
Comments
Hi phola, thank you for reaching out. I assume "navigator" is not available in your test environment (probably pure node nothing linke jsdom). Cheers! |
just checked and this error happens locally too when a component using this hook is included in https://storybook.js.org/ when building storybook (which uses webpack i believe) . Think you are correct maybe a simple |
Hi phola, can you try the file from the issue-branch: In case your CI setup installs all files from the package.json, please add he branch's url instead of the npm-url (https://docs.npmjs.com/cli/v8/configuring-npm/package-json#github-urls) If everything works out, I'll push a new release, but I don't want to litter npm with "trial versions" ti fix this issue :) Thank you :) Cheers! |
@martinkr I've overwritten the local index file from node_modules and still getting the same error. This was supposed to fix it? |
@AlexStefan @martinkr Yep me too |
@AlexStefan i have overwritten the getDefaultLanguage to this: and now it works, i don't know why ? :D |
Hey, thank you for testing. This is exaclty what the new code from 1.3.1 is doing as well (Adjusting the check for navigator to be more robust). The issue is propably that your CI environment does not have a complete DOM. Going to release the new code in a few minutes and going to close the issue afterwards. Cheers1 |
v1.3.1 |
Hi
Many thanks for creating this!
I have an issue with on CI build since v1.3 I think related to auto-detection. any ideas?
The text was updated successfully, but these errors were encountered: