4 ms·
You don’t want to deploy your development tool chain to your production environment, ergo, you want a development environment.
by yakshaving_jgt 4y ago
You don’t want to deploy your development tool chain to your production environment, ergo, you want a development environment.
- crabmusket 4y agoIn the JS world it's common to have hot-reloading development servers, whereas the production environment does not do that. And with the rise of TS, transpilation and bundling are also a thing on the backend, not just for shipping web assets. Once the bundle is done, all your production server needs is `index.js` and `node`, not `tsc`, `webpack` or whatever else you're using.
- airocker 4y ago‘Node’ on dev may run differently than node on production depending on version of dependencies , for eg a shared object file it loads.
- crabmusket 4y agoYes, of course that could happen. All I'm suggesting is that the optimally productive tradeoff is somewhere in between "develop in a full clone of production cloud" and "works on my machine and nowhere else".
- airocker 4y agoI would totally want to deploy on the prod environment. If the tools have their symbols resolved properly, they should run on any reasonable environment. The other way around that we build a dev environment that is different from prod just makes no sense.