<p dir="auto">We should add some basic synchronization around multiple processes creating the node_modules folder at the same time. Basically do whatever <code class="notranslate">cargo build</code> does and have each process wait on the other.</p>
<p dir="auto">This is necessary because it seems like multiple processes creating junctions at the same time causes some weird issues with the junctions becoming invalid. Also, it's duplicate work for the two processes to do this.</p>
<p dir="auto">Edit: I have the code done for this... just need to write a test.</p>
<p dir="auto">I am using deno_core version 0.112.0 in my project. But when I make a release build and run it on another computer without cargo installed I get the following error:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: The system cannot find the path specified. (os error 3)', C:\Users\user\.cargo\registry\src\github.com-1ecc6299db9ec823\deno_core-0.112.0\runtime.rs:390:38"><pre class="notranslate"><code class="notranslate">thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: The system cannot find the path specified. (os error 3)', C:\Users\user\.cargo\registry\src\github.com-1ecc6299db9ec823\deno_core-0.112.0\runtime.rs:390:38
</code></pre></div>
<p dir="auto">It appears to be trying to load <code class="notranslate">00_primordials.js</code> which doesn't exist on my other system. Deno ships in a single executable so i figured that it is possible to do the same with deno_core.</p>