3 ms·
The problem here is that any code run during development could generate code that ends up in production. Even if the dependency isn't used in production, there
by marcus_holmes 8y ago
The problem here is that any code run during development could generate code that ends up in production. Even if the dependency isn't used in production, there is a "compile step" (though it's technically transpiled) during which all sorts of mayhem could ensue.
- hombre_fatal 8y agoAbsolutely. It's like a static site generator having a bunch of dependencies. I just wanted to refine the distinction, though it doesn't really change much. But you can at least be more prudent here than you could with 1,600 production runtime dependencies, like doing your development in an isolated environment on your own machine.