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
audionerd
changed the title
npm start fails with Symbol not found: \_SSL_library_init"
npm start fails with "Symbol not found: _SSL_library_init"
Oct 3, 2017
For now we can work around this issue it by telling socket.io to use ws instead of uws.
ws is worse (in terms of memory usage and performance) than uws, and eventually I'd like to move away from socket.io. But this will solve the problem for now.
After a fresh
npm install
Workaround is to delete
node_modules/uws
folder, which is an optional dependency of socket.io.Could also use
--no-optional
flag tonpm install
A better workaround would be some type of postinstall to delete
uws
.Related: https://github.com/uNetworking/uWebSockets/issues/537
The text was updated successfully, but these errors were encountered: