<h5 dir="auto">System information (version)</h5>
<ul dir="auto">
<li>OpenCV =&gt; 3.4.7</li>
</ul>
<h5 dir="auto">Detailed description</h5>
<p dir="auto">Could <a href="https://docs.opencv.org/3.4.7/d5/d10/tutorial_js_root.html" rel="nofollow">OpenCv.js</a> please be added to <a href="https://www.npmjs.com" rel="nofollow">npm</a> and instructions to install it such as:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="npm install opencvjs --save"><pre class="notranslate"><code class="notranslate">npm install opencvjs --save
</code></pre></div>
<p dir="auto">please be placed in the <a href="https://docs.opencv.org/3.4.7/d0/d84/tutorial_js_usage.html" rel="nofollow">Using OpenCv.js tutorial?</a></p>
<p dir="auto">npm is the main package index for all javascript projects, both browser and Node, and including OpenCv.js there will increase its accessibility to developers significantly.</p>
<p dir="auto">I see there's no package for opencv.js so JavaScript users can install it using <code class="notranslate">npm install</code> as is accustomed by JS users.</p>
<p dir="auto">The benefits of this would be also that is better integrated with web bundlers like webpack, parcel, browserify which simplify development workflow used in generally for web development.</p>
<p dir="auto">I think for supporting this, the .wasm version could be better. BTW the current open.js file, although it works since it supports UMD, it would not be the best since it will be combined by bundlers (so the resulting .js file will contain it and will be huge bloking the user's apps). Instead it should be downloaded separately optionally allowing users to define an alternative url for it (like a CDN).</p>
<p dir="auto">I'm working on a proof f concept for this, and also to support / tests for node.js as API and a little CLI tool too, and I wonder if something like this would be accepted as a PR to at least start the discussion.</p>
<p dir="auto">Thanks</p>