Nvm: installation issue

[ShmidtAlex]

• Operating system and version:
  Ubuntu 16.04.4 LTS
• nvm debug output:
  
  
  there is no nvm command found
  

• nvm ls output:
  
  
  there is no nvm command found
  

• How did you install nvm? (e.g. install script in readme, Homebrew):
  install script in readme
• What steps did you perform?
  it's installation issue
• What happened?
  You have $NVM_DIR set to "~/.nvm", but that directory does not exist. Check your profile files and environment.

• What did you expect to happen?

• Is there anything in any of your profile files (.bashrc, .bash_profile, .zshrc, etc) that modifies the PATH?
  only this one and only in .bashrc:
  export NVM_DIR="/home/alexander/.nvm"
  [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm

- 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...
* Connected to nodejs.org (104.20.22.46) port 443 (#0)
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 604 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
* server certificate verification OK
* server certificate status verification SKIPPED
* common name: .nodejs.org (matched)
* server certificate expiration date OK
* server certificate activation date OK
* certificate public key: RSA
* certificate version: #3
* subject: OU=Domain Control Validated,OU=PositiveSSL Wildcard,CN=.nodejs.org
* start date: Mon, 14 Aug 2017 00:00:00 GMT
* expire date: Wed, 20 Nov 2019 23:59:59 GMT
* issuer: C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO RSA Domain Validation Secure Server CA
* compression: NULL
* ALPN, server accepted to use http/1.1

HEAD /dist/ HTTP/1.1
Host: nodejs.org
User-Agent: curl/7.47.0
Accept: /
Accept-Encoding: deflate, gzip

< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Sat, 12 May 2018 06:36:28 GMT
Date: Sat, 12 May 2018 06:36:28 GMT
< Content-Type: text/html
Content-Type: text/html
< Connection: keep-alive
Connection: keep-alive
< Set-Cookie: __cfduid=dd654ef725649ef688924e0ad9f9ce4b71526106987; expires=Sun, 12-May-19 06:36:27 GMT; path=/; domain=.nodejs.org; HttpOnly
Set-Cookie: __cfduid=dd654ef725649ef688924e0ad9f9ce4b71526106987; expires=Sun, 12-May-19 06:36:27 GMT; path=/; domain=.nodejs.org; HttpOnly
< CF-Cache-Status: EXPIRED
CF-Cache-Status: EXPIRED
< Vary: Accept-Encoding
Vary: Accept-Encoding
< Expires: Sat, 12 May 2018 10:36:28 GMT
Expires: Sat, 12 May 2018 10:36:28 GMT
< Cache-Control: public, max-age=14400
Cache-Control: public, max-age=14400
< 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"
< Server: cloudflare
Server: cloudflare
< CF-RAY: 419adf02cf5a7678-ARN
CF-RAY: 419adf02cf5a7678-ARN
< Content-Encoding: gzip
Content-Encoding: gzip

<

• Connection #0 to host nodejs.org left intact
  

[ShmidtAlex]

Resolve by myself. I just needed to create the directory mkdir ~/.nvm. It was misleading, that in linux files and folders are the same.

[ljharb]

Glad you figured it out :-)