Add - between words in npm scripts

Description

I’m trying to submit my first PR to this awesome project. There were some challenges that I was/am facing e.g.

• I can’t run npm run format from command line on Windows since it complains of not being able to run .sh scripts C:\dev\idea\nx>npm run format

C:\dev\idea\nx>npm run format

> @nrwl/nx-source@10.1.0 format C:\dev\idea\nx
> ./scripts/format.sh

'.' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @nrwl/nx-source@10.1.0 format: `./scripts/format.sh`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @nrwl/nx-source@10.1.0 format script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\vivzt\AppData\Roaming\npm-cache\_logs\2020-09-06T14_40_28_761Z-debug.log

• Running the same format script from my IDE (IntelliJ) results in *.md files changing to have LF line endings and show up as changed.
  • There are few ways we could resolve this issue. One option that comes to mind is adding .gitattributes to make this platform agnostic. I’m open to suggestions and willing to submit a PR for this based on Nx team’s feedback.

---

Now about the trivial change I was trying to submit as my first PR - https://github.com/nrwl/nx/pull/3672 I’d like to suggest that the scripts

• checkcommit
• checkformat
• checkimports
• checkversions

be renamed to:

• check-commit
• check-format
• check-imports
• check-versions

[vivekmore]

I realized my issue was due to the stale state of my node_modules 😞 Running npm i solved the issue for me.

As for adding .gitattributes, thats a step in the right direction, not sure if that’s enough (as you may have already discovered). I’m given to understand that nx team has tried to have the workspace Windows-friendly/compatible but never succeeded in achieving a configuration that was agnostic to MacOS/Linux/Windows operating systems. - Hence I’ve resorted to developing nx in WSL2. background

Although, I share some of your sentiments, but it’s open-source and I can appreciate that the nrwl team needs to prioritize their business over the tool. Moreover, I see this as an opportunity to fix some easy bugs and contribute to an otherwise awesome tool. I’m slightly biased because I’m huge fan of scaffolding tools 😄

[vivekmore]

I tried to reproduce your issue locally, but got stuck somewhere else after:

npm run local-registry enable

My WSL2 doesn’t seem to expose the port 4873