npm scripts

Gulp

<h2>Decision</h2>
<p>We write <a href="https://docs.npmjs.com/cli/v8/using-npm/scripts">scripts</a> into the
<code>scripts</code> section of <code>package.json</code> files and add custom TypeScript scripts to a
<code>scripts</code> folder that we directly call from the <code>scripts</code> block of
<code>package.json</code> where necessary.</p>
<h2>Problems</h2>
<p>The packages and applications we write need scripts to be tested, built,
deployed, and for other tasks that might need to be run from time to time.</p>
<p>Scripts need to integrate with external tools that provide shell-scripts.</p>
<h2>Context</h2>
<p>At the moment, we use a combination of bash scripts, Rush, npm scripts, gulp,
grunt, and JavaScript to run scripts. Understanding a single deployment script
might take you through 11 different files ind 4 different formats.</p>
<h2>Options</h2>
<ul>
<li>Bash scripts</li>
<li>JavaScript script files</li>
<li>TypeScript script files</li>
<li>npm scripts</li>
<li>Gulp</li>
<li>Grunt</li>
</ul>
<h2>Reasoning</h2>
<p>Most scripts we have can be simplified to one line of npm script. The tooling we
use is advanced enough so no major coordination via gulp or grunt is needed.
Using TypeScript script files instead of bash scripts or JavaScript files allows
to more easily use code from the actual package or application in scripts.</p>
<h2>Consequences</h2>
<p>For packages and applications with many or complicated scripts, the
<code>package.json</code> might get complicated. Additional work might be needed to extract
scripts into TypeScript files.</p>
