-
Notifications
You must be signed in to change notification settings - Fork 46
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
Building a bundle for Browsers fails #72
Comments
Thank you for looking into this, I haven't tested browser builds in a while. Does pinning the version to 3.0.2 in the SDK's package.json help? |
Not sure, the browser build process works, but two of tests (51 and 52) fail with Firefox 83.0 (they all pass in Firefox 85.0b1 and Chrome). Console Log: Click to expand
Also at the end of the console log there are 6 |
While typing my reply, above, I noticed that there was an incoming update to Firefox - retesting with this updated version Firefox 84.0 the tests all pass. So it looks as if pinning Not looked into all the changes that Firefox 84.0 brings. But, I do know that it corrects a long standing issue with the handling of localhost, adding support for localhost subdomains. |
Sweet, thank you for looking into this. Would you be down to submit a pull request for pinning the version? |
Should be able to put together a PR. |
A temp. fix for RangerMauve#72
Think I've found the underlying problem. The problem is with the If I clone the sodium-universal repo alongside the sdk repo, run I'm going to close the PR. |
Closing this. The release of [email protected] has fixed this issue. |
Looks to be cause by a problem reported upstream as sodium-friends/sodium-universal#6
npm run build
fails with:Oh, and there is a missing
npm install
betweencd sdk
andnpm run build
in the readme.The text was updated successfully, but these errors were encountered: