-
Notifications
You must be signed in to change notification settings - Fork 141
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
Using with typescript/angular #179
Comments
I get the warning too and just ignore it. I don't get the error. How are you building? Angular-cli? Custom webpack? I use libsodium.js with angular-cli. Feel free to look at my configuration. |
OK, I have a bare project that's failing now. I can reproduce it like so.
|
There's two ways to fix this. You could install the package path
You can read me here. From what I understand libsodium references path. path is a node thing and doesn't exist in the browser. Libsodium on a browser doesn't actually make use of path but it seems to need it in order to be bundled. Therefore you can set path to be anything or polyfill it. Ah Javascript... |
Thank you, that fixed it! |
I did an
npm install libsodium-wrappers
but when I try and build I get this:Are there other npm modules that are required?
The text was updated successfully, but these errors were encountered: