uNetworking / uWebSockets.js

μWebSockets for Node.js back-ends :metal:
Apache License 2.0
8.08k stars 574 forks source link

Error: Cannot find module './uws_linux_x64_102.node' #781

Closed bugs181 closed 2 years ago

bugs181 commented 2 years ago

Related #627

Unfortunately, I'm still receiving this error even though my system appears like it meets all requirements.

Installation

$ npm install uNetworking/uWebSockets.js#v20.10.0

added 1 package, and audited 2 packages in 3m

found 0 vulnerabilities

Error

$ node index
/.../ProjectName/node_modules/uWebSockets.js/uws.js:22
                throw new Error('This version of uWS.js supports only Node.js 14, 16 and 18 on (glibc) Linux, macOS and Windows, on Tier 1 platforms (https://github.com/nodejs/node/blob/master/BUILDING.md#platform-list).\n\n' + e.toString());
                ^

Error: This version of uWS.js supports only Node.js 14, 16 and 18 on (glibc) Linux, macOS and Windows, on Tier 1 platforms (https://github.com/nodejs/node/blob/master/BUILDING.md#platform-list).

Error: Cannot find module './uws_linux_x64_102.node'

System:

(kernel >= 4.18)
$ uname -r
5.11.0-7620-generic

(glibc >= 2.28)
$ ldd --version
ldd (Ubuntu GLIBC 2.32-0ubuntu3) 2.32 

$ node --version 
v17.4.0

Let me know if I'm missing any information or can test further. Thanks.

bugs181 commented 2 years ago

By your own words in reply, is this not correct?

Since this is closed, does this mean node 17 is supported now?

And as of v20.1.0, this is fixed. Thank you!

Originally posted by @FallingSnow in https://github.com/uNetworking/uWebSockets.js/issues/627#issuecomment-950397649

Yes please test it out and also test SSL. These binaries now use BoringSSL

Originally posted by @alexhultman in https://github.com/uNetworking/uWebSockets.js/issues/627#issuecomment-950400349

In the first quote, by this I assume that meant the OP issue of Nodejs v17 support

627 @FallingSnow said it is fixed. You replied with Yes

What was the "Yes" in response to? From my perspective it was either this is fixed or does this mean node 17 is supported now.

Please, tell me where my assumption was wrong.