No. Papa Parse has no dependencies. If jQuery is present, however, it plugs in to make it easier to select files from the DOM.
No. Papa Parse has no dependencies. If jQuery is present, however, it plugs in to make it easier to select files from the DOM.
</p>
</p>
<h6id="combine">Can I put other libraries in the same file as Papa Parse?</h6>
<p>
Yes, but then don't use the Web Worker feature unless your other dependencies are battle-hardened for worker threads. A worker thread loads an entire file, not just a function, so all those dependencies would be executed in an environment without a DOM and other <code>window</code> features. If any of those dependencies crash (<code>Cannot read property "defaultView" of undefined</code><ahref="https://github.com/mholt/PapaParse/issues/114">is</a><ahref="https://github.com/mholt/PapaParse/issues/163">common</a>), the whole worker thread will crash and parsing will not succeed.
</p>
<h6id="browsers">Which browsers is it compatible with?</h6>
<h6id="browsers">Which browsers is it compatible with?</h6>
<p>
<p>
@ -94,11 +99,6 @@
Yes. But if you want to use Web Workers, you'll need to specify the relative path to Papa Parse. To do this, set <ahref="/docs#readonly">Papa.SCRIPT_PATH</a> to the relative path of the Papa Parse file. In synchronous loading, this is automatically detected.
Yes. But if you want to use Web Workers, you'll need to specify the relative path to Papa Parse. To do this, set <ahref="/docs#readonly">Papa.SCRIPT_PATH</a> to the relative path of the Papa Parse file. In synchronous loading, this is automatically detected.
</p>
</p>
<h6id="combine">Can I build Papa Parse into the same file with other JS dependencies?</h6>
<p>
Yes, but then don't use the Web Worker feature unless your other dependencies are battle-hardened for worker threads.
</p>
<h6id="open-source">Is it open source? (Can I contribute something?)</h6>
<h6id="open-source">Is it open source? (Can I contribute something?)</h6>