Use npm-run-all to run test and lint scripts

[bmish]

• Reorganizes test and lint NPM scripts with popular tool npm-run-all
• Adds convenient scripts for running different types of linting or tests
• Runs linting in parallel but keeps output of linters separate
• Does not run linting and testing in parallel, since this would break the real-time/live output from ava
• Shows complete output from all types of linting and tests, even if one type fails (previously, the test script would exit early if one type failed, so you wouldn't be able to see all the failures)
• Avoids using && which might not have as good of cross-platform support according to the npm-run-all readme

[fisker]

I suggest also add a fix version.

[fisker]

I believe only double quote is supported on Windows.

[bmish]

Fixed.

[bmish]

I suggest also add a fix version.

Added :fix scripts.

[fisker]

Sorry, I didn't make myself clear.

I prefer

{
	"lint": "",
	"lint:a": "",
	"lint:b": "",
	"fix": "",
	"fix:a": "",
	"fix:b": ""
}

yarn fix and yarn fix:js is simpler than yarn lint:fix and yarn lint:js:fix

WDYT?

Here is how I use.

[bmish]

@fisker that's fine with me, updated.

[fisker]

Can you also update the action config file? https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/.github/workflows/main.yml#L28

[bmish]

Can you also update the action config file? main/.github/workflows/main.yml#L28

Updated to have CI run npm run lint and npm run test:js.

However, this is why I personally prefer to have the test and lint scripts completely independent, so that CI can just run the lint and test scripts separately.

[fisker]

Me too. But I guess sindresorhus prefers it in one.

[bmish]

It looks like Windows CI doesn't like something about running nyc ava even though the tests appear to have passed.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! eslint-plugin-unicorn@38.0.1 test:js: `nyc ava`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the eslint-plugin-unicorn@38.0.1 test:js script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

[fisker]

Try switch nyc to c8?

[bmish]

Try switch nyc to c8?

I doubt nyc itself is the problem as I've used that in other repos with Windows CI.

[fisker]

I ran into similar thing, and fixed by using c8. But I'm not sure, we can figure later.