Add npm scripts

[RyanZim]

https://github.com/RyanZim/awesome-npm-scripts

I couldn't find an awesome list relating to npm scripts and using npm as a build tool, so I wrote one. This is a resubmission of #775; the list has been expanded since then.

By submitting this pull request I confirm I've read and complied with the below requirements.

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

• I have read and understood the contribution guidelines and the instructions for creating a list.
• This pull request has a descriptive title.
  For example, Add Name of List, not Update readme.md or Add awesome list.
• The entry in the Awesome list should:
  • Include a short description about the list project/theme. It should not describe the list itself.
    Example: - [Fish](…) - User-friendly shell.
  • Be added at the bottom of the appropriate category.
• The list I'm submitting complies with these requirements:
  • Has been around for at least 30 days.
    That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
  • It's the result of hard work and the best I could possibly produce.
  • Non-generated Markdown file in a GitHub repo.
  • The repo should have the following GitHub topics set: awesome-list, awesome, list. I encourage you to add more relevant topics.
  • Not a duplicate.
  • Includes a succinct description of the project/theme at the top of the readme. (Example)
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Includes a project logo/illustration whenever possible.
    • Placed at the top-right of the readme. (Example)
    • The image should link to the project website or any relevant website.
    • The image should be high-DPI. Set it to maximum half the width of the original image.
  • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
  • Has the Awesome badge on the right side of the list heading,
  • Has a Table of Contents section.
    • Should be named Contents, not Table of Contents.
    • Should be the first section in the list.
  • Has an appropriate license.
    • That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
    • If you use a license badge, it should be SVG, not PNG.
  • Has contribution guidelines.
    • The file should be named contributing.md. Casing is up to you.
  • Has consistent formatting and proper spelling/grammar.
    • Each link description starts with an uppercase character and ends with a period.
      Example: - [AVA](…) - JavaScript test runner.
    • Drop all the A / An prefixes in the descriptions.
    • Consistent naming. For example, Node.js, not NodeJS or node.js.
  • Doesn't include a Travis badge.
    You can still use Travis for list linting, but the badge has no value in the readme.
• Go to the top and read it again.

[legodude17]

Not followed:

• Drop all the A / An prefixes in the descriptions.
• Each link description starts with an uppercase character and ends with a period.

Advanced front-end automation with npm scripts - by Kate Hudson

This one needs an actual description.

[RyanZim]

@legodude17 Thanks for the review. Fixed (I think)!

[legodude17]

Suggestions:

• Actually describe what watch and onchange do.
• Find a way to reword the Cross-Platform Utilities section so less of them start with the words cross-platform
• Describe what shx is

[RyanZim]

Hey, thanks for the suggestions.

watch and onchange both do the same thing; they watch files. The only difference is the command syntax. Would it be OK to describe what they do directly under the heading and leave the individual descriptions pretty close to what they are?

[legodude17]

Yeah, that would make sense, as long as you make it clear that the description applies to both of them.

[RyanZim]

@legodude17 Can you take a look at RyanZim/awesome-npm-scripts#18?

[legodude17]

@RyanZim Very nice!

I would suggest you improve the description of shx, like give examples.

[RyanZim]

@legodude17 Updated RyanZim/awesome-npm-scripts#18

[legodude17]

@RyanZim Very nice! I don't think I have anything else to add.

Any thoughts @sindresorhus?

[RyanZim]

Any action on this?

[RyanZim]

@sindresorhus ping?

[sindresorhus]

Includes a succinct description of the project/theme at the top of the readme. (Example)

⬆️

[RyanZim]

@sindresorhus Change LGTM

[RyanZim]

@sindresorhus Updated

[sindresorhus]

Added :)

[RyanZim]

Thanks a lot!