You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is the right place to ask this question, but we're running into some extreme build lag due to our use of node-sodium, because of the time it takes Travis to perform an NPM install.
One thing I wanted to try doing was create a pre-built node-sodium in a privately controlled repo within my organization, similar to how they are maintained for Windows, but I'm not familiar enough with how I might do something like this.
Are there any existing guides or documentation that could teach me how we could accomplish something like this. I'd much rather incur the overhead of keeping a lib up to date, rather than slow down our dev process, if there is a way to do it.
Thanks!
The text was updated successfully, but these errors were encountered:
I'm not sure if this is the right place to ask this question, but we're running into some extreme build lag due to our use of node-sodium, because of the time it takes Travis to perform an NPM install.
One thing I wanted to try doing was create a pre-built node-sodium in a privately controlled repo within my organization, similar to how they are maintained for Windows, but I'm not familiar enough with how I might do something like this.
Are there any existing guides or documentation that could teach me how we could accomplish something like this. I'd much rather incur the overhead of keeping a lib up to date, rather than slow down our dev process, if there is a way to do it.
Thanks!
The text was updated successfully, but these errors were encountered: