Skip to content
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

npm start fails with "Symbol not found: _SSL_library_init" #735

Closed
audionerd opened this issue Oct 3, 2017 · 1 comment
Closed

npm start fails with "Symbol not found: _SSL_library_init" #735

audionerd opened this issue Oct 3, 2017 · 1 comment
Assignees
Milestone

Comments

@audionerd
Copy link
Member

audionerd commented Oct 3, 2017

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 to npm install

A better workaround would be some type of postinstall to delete uws.

Related: https://github.com/uNetworking/uWebSockets/issues/537

@audionerd audionerd self-assigned this Oct 3, 2017
@audionerd audionerd added this to the Beta 13 milestone Oct 3, 2017
@audionerd 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
@audionerd audionerd added this to IN PROGRESS in Features for RC1 Oct 3, 2017
@audionerd
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant