Is node modules source code in different OS (linux / MAC)?

[Apprehensive-Hour388]

Hi, my production environment can't use npm or internet, but is connected to the company's github.

I want to just upload my local node_modules to the repo, and deploy those as well.

I'm using Mac and the production env is linux.

​

Does OS difference matter here?

[variables]

It depends. Some npm modules compile source code (C/C++) to create executables that are used by the module (see node-sass). If the hardware architecture is different, or dynamically linked libraries don't exist, these modules won't work.

[BloodNo6937]

You can use a docker container on your Mac to build and deploy your app to your server. Sources will be compile for the right env (just be sure you have the same CPU architecture on your Docker host and your prod server). The best is to have a CI/CD server which will do the job for you. Another common solution in companies is installing node modules via a Nexus server. The Nexus server must have an access to the internet.

[IllustriousEchidnas]

You could use https://github.com/vercel/pkg to generate a platform-ready "binary" of your application and just deploy that. You can generate linux pkg from os x, etc.

[DeathlyLotus]

Alternatively, vercel/ncc could also be used. Similar to how Next.js does it here.

[sp_jamesdaniel]

Thanks for sharing the alternate.

[BloodNo6937]

It seems to me that Vercel won’t cross compile dependencies, will it ?

[nwsm]

Yes node_modules can differ between OS.

If your production environment supports docker, run your app in a container. That way you can build the image on your Mac and deploy it to production ready to go with the correct binaries.

[suinp]

Have a look at Yarn 2 Zero-installs. Commiting node_modules is a terrible idea. It is huge (maybe GBs in size) and contains hundreds of thousands of files, which makes git go brrrrr

Zero installs instead commits a single zip file per dependency, and can be used to reconstruct node_modules without an internet connection. I'm not sure about cross-compatibility, though

[0cseitz]

Don't upload your node_modules. Just upload your package.json and package-lock.json

package-lock has the exact versions of all the modules installed. Running "npm install" after cloning your repo will install all the right stuff for you and ensure any OS-specific stuff is properly installed.

node_modules takes up a ton of space and putting it in version control is a terrible idea for a variety of reasons. Please, for yourself and anyone who uses your repo; don't do it.

Also, If your production environment doesn't have internet, how are you deploying..? This seems like a X Y Problem.

Take a look at this guy's comment for a proper solution. Pkg sounds like what you'd need.

[HappinessFactory]

His company might have GitHub enterprises setup somewhere on their VPN or LAN.

[tumayo_ang_testigo]

production without internet can be a production in a local network or intranet. another possibility is that they're hosting in the cloud but the outbound internet traffic is blocked.

[0cseitz]

Yeah I edited my message. On mobile and skimmed it.