<blockquote>
<p dir="auto">got an error after pressing ^C:<br>
npm ERR! cb() never called!</p>
</blockquote>

<p dir="auto">Full Error:<br>
npm ERR! cb() never called!</p>
<p dir="auto">npm ERR! This is an error with npm itself. Please report this error at:<br>
npm ERR!     <a href="https://npm.community" rel="nofollow">https://npm.community</a></p>
<p dir="auto">npm ERR! A complete log of this run can be found in:<br>
npm ERR!     /Users/okleodai/.npm/_logs/2020-01-07T02_31_32_703Z-debug.log</p>
<blockquote>
<p dir="auto">Complete Log:<br>
0 info it worked if it ends with ok<br>
1 verbose cli [<br>
1 verbose cli   '/usr/local/Cellar/node/12.10.0/bin/node',<br>
1 verbose cli   '/usr/local/bin/npm',<br>
1 verbose cli   'start'<br>
1 verbose cli ]<br>
2 info using npm@6.12.0<br>
3 info using node@v12.10.0<br>
4 verbose run-script [ 'prestart', 'start', 'poststart' ]<br>
5 info lifecycle picss@0.1.0<del>prestart: picss@0.1.0<br>
6 info lifecycle picss@0.1.0</del>start: picss@0.1.0<br>
7 verbose lifecycle picss@0.1.0<del>start: unsafe-perm in lifecycle true<br>
8 verbose lifecycle picss@0.1.0</del>start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/okleodai/Desktop/Tech/webdev2/prod/picss/node_modules/.bin:/Users/okleodai/.rbenv/shims:/anaconda3/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Users/okleodai/.rbenv/shims:/anaconda3/bin<br>
9 verbose lifecycle picss@0.1.0<del>start: CWD: /Users/okleodai/Desktop/Tech/webdev2/prod/picss<br>
10 silly lifecycle picss@0.1.0</del>start: Args: [ '-c', 'react-scripts start' ]<br>
11 silly lifecycle picss@0.1.0~start: Returned: code: null  signal: SIGINT<br>
12 timing npm Completed in 8166154ms<br>
13 error cb() never called!<br>
14 error This is an error with npm itself. Please report this error at:<br>
15 error <a href="https://npm.community" rel="nofollow">https://npm.community</a></p>
</blockquote>
<h1 dir="auto">What / Why</h1>
<p dir="auto">As a developer you would like to leave comments in the same context as you write code to note down todo's, leave hints for other devs or other reasons. Most of my code allows for this except for <code class="notranslate">package.json</code>, at least, there is no standard. After reading <a href="https://dev.to/napolux/how-to-add-comments-to-packagejson-5doi" rel="nofollow">this blog</a> I think this should be a standard, in a way that more people use the same notation and my IDE or VSC highlights comments as a comment.</p>
<h2 dir="auto">When</h2>
<ul dir="auto">
<li>at code-time</li>
</ul>
<h2 dir="auto">Where</h2>
<p dir="auto"><code class="notranslate">package.json</code></p>
<h2 dir="auto">How</h2>
<p dir="auto">The proposed standard (for now) is that above a specific property in an array, you note down the same property prefixed with <code class="notranslate">@comment&lt;space&gt;</code>.</p>
<h3 dir="auto">Current Behavior</h3>
<ul dir="auto">
<li><code class="notranslate">@comment</code> is not a common standard</li>
<li>if this is done and agreed in this context, I can follow through and talk to IDE's repos</li>
</ul>
<ul dir="auto">
<li>n/a</li>
</ul>
<h3 dir="auto">Expected Behavior</h3>
<ul dir="auto">
<li><code class="notranslate">@comment</code> is not a common standard</li>
</ul>
<ul dir="auto">
<li>n/a</li>
</ul>
<h2 dir="auto">Who</h2>
<ul dir="auto">
<li>n/a</li>
</ul>
<h2 dir="auto">References</h2>
<p dir="auto"><a href="https://dev.to/napolux/how-to-add-comments-to-packagejson-5doi" rel="nofollow">this blog</a></p>
<ul dir="auto">
<li>n/a</li>
</ul>