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
First I used nvm install node, then nvm use node. After this I checked my node version using node -v and it said v17.1.0. So far so good.
What happened?
Then I tried to use nvm install 14.16.1 but got the error: curl: (22) The requested URL returned error: 404
This is how it looked, and after the last line it went bananas and pretty much into what looked like an endless loop of lots of text about configuration stuff (or smth).
Downloading and installing node v14.16.1...
Downloading https://nodejs.org/dist/v14.16.1/node-v14.16.1-darwin-arm64.tar.xz...
curl: (22) The requested URL returned error: 404
Binary download from https://nodejs.org/dist/v14.16.1/node-v14.16.1-darwin-arm64.tar.xz failed, trying source.
grep: /Users/ozgur/.nvm/.cache/bin/node-v14.16.1-darwin-arm64/node-v14.16.1-darwin-arm64.tar.xz: No such file or directory
Provided file to checksum does not exist.
Binary download failed, trying source.
Clang v3.5+ detected! CC or CXX not specified, will use Clang as C/C++ compiler!
Local cache found: ${NVM_DIR}/.cache/src/node-v14.16.1/node-v14.16.1.tar.xz
Checksums match! Using existing downloaded archive ${NVM_DIR}/.cache/src/node-v14.16.1/node-v14.16.1.tar.xz
$>./configure --prefix=/Users/ozgur/.nvm/versions/node/v14.16.1 <
Node.js configure: Found Python 3.8.9...
INFO: configure completed successfully
What did you expect to happen?
I expected the 14.16.1 version to be installed. I installed nvm on my old macbook air laptop earlier today and it seemed to work flawlessly so I don't understand what mistake I did now running the installation again. Could it be the M1 chip that is the issue?
Is there anything in any of your profile files that modifies the PATH?
Not sure, but I don't think so.
If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?
* Trying 104.20.22.46:443...
* Connected to nodejs.org (104.20.22.46) port 443 (#0)* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
* CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server accepted to use h2
* Server certificate:
* subject: OU=Domain Control Validated; OU=PositiveSSL Wildcard; CN=*.nodejs.org
* start date: Oct 21 00:00:00 2019 GMT
* expire date: Jan 18 23:59:59 2022 GMT
* subjectAltName: host "nodejs.org" matched cert's "nodejs.org"* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA* SSL certificate verify ok.* Using HTTP2, server supports multi-use* Connection state changed (HTTP/2 confirmed)* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0* Using Stream ID: 1 (easy handle 0x13e010600)> HEAD /dist/ HTTP/2> Host: nodejs.org> user-agent: curl/7.77.0> accept: */*> accept-encoding: deflate, gzip> * Connection state changed (MAX_CONCURRENT_STREAMS == 256)!< HTTP/2 200 HTTP/2 200 < date: Mon, 29 Nov 2021 21:47:42 GMTdate: Mon, 29 Nov 2021 21:47:42 GMT< content-type: text/htmlcontent-type: text/html< last-modified: Mon, 29 Nov 2021 18:15:06 GMTlast-modified: Mon, 29 Nov 2021 18:15:06 GMT< cache-control: max-age=14400cache-control: max-age=14400< cf-cache-status: HITcf-cache-status: HIT< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"< vary: Accept-Encodingvary: Accept-Encoding< server: cloudflareserver: cloudflare< cf-ray: 6b5f0934c805cb08-ARNcf-ray: 6b5f0934c805cb08-ARN< content-encoding: gzipcontent-encoding: gzip< * Connection #0 to host nodejs.org left intact
The text was updated successfully, but these errors were encountered:
Operating system and version:
macOS Monterey version 12.0.1
MacBook Pro, M1 Pro chip.
nvm debug
output:nvm ls
output:How did you install
nvm
?I installed it using the curl script
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
What steps did you perform?
First I used nvm install node, then nvm use node. After this I checked my node version using node -v and it said v17.1.0. So far so good.
What happened?
Then I tried to use nvm install 14.16.1 but got the error: curl: (22) The requested URL returned error: 404
This is how it looked, and after the last line it went bananas and pretty much into what looked like an endless loop of lots of text about configuration stuff (or smth).
What did you expect to happen?
I expected the 14.16.1 version to be installed. I installed nvm on my old macbook air laptop earlier today and it seemed to work flawlessly so I don't understand what mistake I did now running the installation again. Could it be the M1 chip that is the issue?
Is there anything in any of your profile files that modifies the
PATH
?Not sure, but I don't think so.
If you are having installation issues, or getting "N/A", what does
curl -I --compressed -v https://nodejs.org/dist/
print out?The text was updated successfully, but these errors were encountered: