-
Notifications
You must be signed in to change notification settings - Fork 127
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
Angular/typescript usage #143
Comments
Not that I know of. Never used it in the browser.
On Mon, Dec 3, 2018 at 00:52 grosch ***@***.***> wrote:
Are there examples of how to use this with angular?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#143>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAT9XkF_2ZqiE-QE1HgpBc14DmuPW0xIks5u1LwygaJpZM4Y969E>
.
--
Do It Right or Don't Do It At All!
|
After doing the
I'm doing this on macOS Mojave. During the install I saw a bunch of warnings about deprecated methods being called but it did succeed. |
The deprecations are from libsodium and should not cause issues. It seems that NG cannot find the binary module for sodium. Can you check the build directory under node sodium to see if it is there after node sodium install runs successfully? |
% find . -name libsodium.a
./node_modules/sodium/deps/libsodium/src/libsodium/.libs/libsodium.a
./node_modules/sodium/deps/build/lib/libsodium.a
% pushd node_modules/sodium/lib/keys
% ls ../../build/Release/
nothing.a obj.target/ sodium.node* |
I get the same errors. Any work around for using it with angular? |
Are there examples of how to use this with angular?
The text was updated successfully, but these errors were encountered: