3 ms·
Yeah, that made me laugh. Is it really a relief to have a config file you can't see instead of one you can?
by l_t 8y ago
Yeah, that made me laugh. Is it really a relief to have a config file you can't see instead of one you can?
- dictum 8y agoGiven `vue inspect` or even a `console.log(config)` inside the `configureWebpack` function in vue.config.js, it's very much a config file you can see.
- l_t 8y agoFair enough -- it's not like it's completely opaque. But when I start a project and see there is no webpack.config.js in the project root, I feel the opposite of relief. For example, if there isn't a config file, it's usually because there are more than one. Or, even worse, the config is dynamically generated. A build process like that is much harder for me to fully understand than one with a simple webpack.config.js. However, this may be biased, as it's coming from the perspective of someone who already "knows Webpack".