Asher

> But I'm not sure how would having the node_modules folder from one arch would affect another arch This is exactly why I have avoided doing that todo so far...

> Today there is never a yarn in build-release.sh Ah yup it is done in a previous step and then this step has an option (`KEEP_MODULES`) for whether to also...

Yeah I say we go ahead with this plan.

> KEEP_MODULES never seems used Yup, from what I recall initially we never kept the modules then later `KEEP_MODULES` was added to make building locally faster (so you would not...

Er wait I might have misunderstood. We do already run `yarn --production` so those things exist in the standalone already but now the npm package will include them when it...

I think we would need to look into how exactly this installs code-server. Is there a recipe somewhere? I have no experience with conda.

Thank you for the link! It appears to download the standalone releases from GitHub so I tried replicating by downloading and running it on an Ubuntu host: ``` $ wget...

Ah, I was thinking that since the `code-server` script Conda installs invokes plain `node` then depending on your path or the last version of Node you installed it could be...

Uhh yeah `/opt/code-server/lib/vscode/bin/remote-cli/code-server` is a VS Code thing, not our script. Maybe we should remove it during the packaging step since I have no idea if it would even work...

Or maybe we patch to prevent it from getting added to the `PATH`? Or patch to add our own script to the path instead.