docs(install): instruct to use npm explore in non-git repo warning

[Tapppi]

Fixes #104

[Tapppi]

Dont know if the docs type makes sense, or if it should be style/refactor.. Sorry I'm still fairly new to the angular format 😞 Also forgot the fixes footer from the commit.. Ah crap.

[codecov-io]

Current coverage is 100%

Merging #105 into master will not change coverage

@@            master      #105   diff @@
========================================
  Files            4         4          
  Lines          114       114          
  Methods          0         0          
  Messages         0         0          
  Branches         4         4          
========================================
  Hits           114       114          
  Misses           0         0          
  Partials         0         0          

Powered by Codecov. Last updated by 73262f4...04585a1

[ta2edchimp]

You could use git commit --amend to alter you last commits' message (I'd say style or sth. but am unsure as well considering this particular example) and force push to your remote branch. This PR would update automatically afterwards.

While thinking about it, personally I'd say even make it a fix (this would trigger a new semantic release after merging).

[kentcdodds]

This looks fine to me. I probably wouldn't call this a docs change but a fix. But lucky for both of us, GitHub now allows me to update your commit message for you!

I'll go ahead and merge this and update the message for you :-) Thanks for the contribution!

[Tapppi]

Thank you for the quick response! 👍