3 ms·
> It is absolutely trivial to use different proxies in different environment based on env vars, local files, etc. For something to be "absolutely trivial", you
by nawgz 4y ago
> It is absolutely trivial to use different proxies in different environment based on env vars, local files, etc.
For something to be "absolutely trivial", you would expect the average user to be able to produce trivial-looking configuration. It is certainly not the case with any Java program I've seen which has to handle two build environments.
On the other hand, all my NodeJS projects show absolutely no sign they had to be "adapted" to the second+ environment.
But sure, we can pretend Java package management is up to snuff, just throw some more "it's trivial"-type aphorisms around
- ElectricalUnion 4y agoIME npm sucks even more that Java if you really need to change repositories ( not just proxy ). I was stuck under very old (and deprecated) versions of node and NPM, and at my $OLDJOB lockfiles were respected with a CI under restrictive proxy service and alternative npm repo. "delete lockfile, npm install everything again with correct repository under VPN" was a very recurring thing on every project where someone thought "it's just a npm install, what could go wrong?".