Use a semi-script-runner to remove yarn dependency from package.json about typescript-starter

[bitjson]

I was intentionally requiring the use of yarn (because it's fantastic and eliminates a lot of potential headaches), but I don't have a particularly strong opinion about it. Is there a good reason not to use yarn?

[Alxandr]

No. It's just a good idea not to force people to use it. Without the yarn run x && yarn run y scripts, you enable people to run whatever "thing that can run scripts from package.json" without having what you use installed. As far as I know there are a few of them out there (though afaik yarn and NPM is by far the most used). I just remember this really annoying me on a lot of packages when I switched to yarn, that most packages I worked on used npm run x && npm run y requiring npm. This is why I made the simple-scripts in the first case.

[bitjson]

Thanks for opening this issue @Alxandr – I just made things a little better here: 45d7dfa

I'd still like to keep yarn as part of the starter (since I think all JS libraries should probably be using it now), and I don't really want to add an extra dependency for a small percentage of users. I updated the examples though. Hopefully that will make them more generally approachable.

Closing this for now, but please let me know if I should reopen.