Update README.md

added WSL troubleshooting and provided an solution to a common issue (fixed typos)
This commit is contained in:
mattjaf 2022-11-30 19:29:27 -08:00 committed by GitHub
parent ff091f6afc
commit 11b308ae8b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -54,7 +54,7 @@
- [Docker For Development Environment](#docker-for-development-environment) - [Docker For Development Environment](#docker-for-development-environment)
- [Problems](#problems) - [Problems](#problems)
- [macOS Troubleshooting](#macos-troubleshooting) - [macOS Troubleshooting](#macos-troubleshooting)
- [wsl Troubleshooting](#wsl-troubleshooting) - [WSL Troubleshooting](#wsl-troubleshooting)
- [Maintainers](#maintainers) - [Maintainers](#maintainers)
- [License](#license) - [License](#license)
- [Copyright notice](#copyright-notice) - [Copyright notice](#copyright-notice)
@ -981,7 +981,7 @@ Here's what you will need to do:
Now you should be able to use node as usual. Now you should be able to use node as usual.
## wsl Troubleshooting ## WSL Troubleshooting
If you've encountered this error on wsl-2 If you've encountered this error on wsl-2
```sh ```sh
@ -994,7 +994,7 @@ It may be due to your antivirus, vpn, or other reasons.
Where you can `ping 8.8.8.8` while you can't `ping google.com` Where you can `ping 8.8.8.8` while you can't `ping google.com`
This could be simply be solved by running in your root directory: This could be simply be solved by running this in your root directory:
```sh ```sh
sudo rm /etc/resolv.conf sudo rm /etc/resolv.conf