I noticed something interesting with a Vue app I’m working. If I run it with “npm run serve”, it runs fine, but obviously I can’t use local Netlify functions. If I run with “ntl dev”, it still works fine, but I get an incredible amount of console messages. Here is an example:
Were you able to confirm that running the -c flag did indeed change the command that dev run to spin up the Vue process? Wondering if instead you might want to define the dev parameters a tad more declaratively in your Netlify.toml file as described in (this link is to a specific header in the document, “netlify.toml [dev] block”)
From what I could see, using -c "npm run serve" did not change the output, it was still verbose. I don’t know what ntl is doing to make the output more verbose. Looking at ntl dev --help, I don’t see an option to make itself a bit more verbose so I can see what it’s doing.
Well digging into the dev code further, it looks like the inferred command for a vue project would be vue-cli-service serve so perhaps that’s where the verbosity is coming from? Not a vue user myself so not sure I’d say try the Netlify.toml [dev] configuration and see if that helps
Seems like that might be something eventually running webpack --progress - perhaps there’s a webpack config somewhere that specifies it off the command line since that is supposed to be possible (cf https://webpack.js.org/api/cli/)?