Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix typo on paragraph 11. Plus some minor formatting proposals #272

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix typo on paragraph 11. Plus some minor formatting proposals #272

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions doc/RECOMMENDATIONS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
## Recommendations :ok_hand:

- It is highly recommended to install node and npm via brew or nvm or n or similars
- It is highly recommended (when developing or testing ndm) to not start the app with `sudo` (WRONG! `sudo npm run...`)
- It is highly recommended to install node and npm via `brew` or `nvm` or n or similars
- It is highly recommended (when developing or testing `ndm`) to not start the app with `sudo` (WRONG! `sudo npm run...`)
- It is highly recommended to not rename `node_modules/` folder in your projects (which is a standard naming for node pkgs folder and should never be renamed)
- It is recommended to manage only versioned projects with ndm (git, svn, mercurial etc..). This way everything can be reverted to it's previous/original status in case of unlikely events that gone wrong.
- It is recommended to install and always use the LTS node version (brew or nvm or n or similars will help you to manage this with comfort)
- It is recommended to manage only versioned projects with `ndm` (git, svn, mercurial etc..). This way everything can be reverted to it's previous/original status in case of unlikely events that gone wrong.
- It is recommended to install and always use the LTS node version (`brew` or `nvm` or n or similars will help you to manage this with comfort)
- It is highly recommended to fix npm permissions on your machine (if not already fixed). This means no more `sudo` for global actions. How to fix permissions is simple and written here: https://docs.npmjs.com/getting-started/fixing-npm-permissions
- It is recommended to always run the latest version of ndm
- It is recommended to always run the latest version of `ndm`
- It is highly reccomended to not install packages globally if those packages aren't meant/developed to be installed globally. You might face strange problems when trying to uninstall them and probably other related problems.
- It is recomended to not change default npm configs, npm config and the use of .npmrc aren't yet fully supported by ndm (we will remove this recommandation as soon has these features will be implemented/supported)
- It is recomended to not change default npm configs, npm config and the use of .npmrc aren't yet fully supported by ndm (we will remove this recommendation as soon has these features will be implemented/supported)

🌈 Happy npm desktop managing!