-
Notifications
You must be signed in to change notification settings - Fork 233
chore(repo): update CONTRIBUTING.md #2443
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.
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
base: master
Are you sure you want to change the base?
Conversation
|
View your CI Pipeline Execution ↗ for commit e4e1a37.
☁️ Nx Cloud last updated this comment at |
isaacplmann
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes you added are helpful.
It would be good to add a note near the beginning stating that people should file an issue before making a PR to make sure that their code changes make sense before they do the actual work.
| - Install Node.js | ||
| - Install yarn: https://classic.yarnpkg.com/en/docs/install | ||
| - Run yarn install in the root directory | ||
| - Install java: https://www.java.com/en/download/help/download_options.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be helpful to list which version(s) to install
|
|
||
| ### How to find Nx Console logs | ||
|
|
||
| Regardless of your IDE, there might be relevant information in the `daemon.log` & `daemon-error.log` files. You can find their location by running `nx daemon --log`. </br> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The HTML closing tag </br> is not valid HTML. For line breaks, use either the self-closing tag <br/> or the shorter form <br>. Both are valid in HTML5 and will render correctly in most contexts.
| Regardless of your IDE, there might be relevant information in the `daemon.log` & `daemon-error.log` files. You can find their location by running `nx daemon --log`. </br> | |
| Regardless of your IDE, there might be relevant information in the `daemon.log` & `daemon-error.log` files. You can find their location by running `nx daemon --log`. <br/> |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
No description provided.