Is your proposal related to a problem?
It's annoying having to deploy and check whether your improvements have worked or not, we can't get the localhost server to verify if lighthouse in devtools passes to a reasonable score.
Describe the solution you'd like
Whilst developing and fixing issues with lighthouse in devtools, it would be nice, on localhost we can provide an argument npm run start --compress=true so locahost serves compress gzipped CSS and JS etc.
This will prevent me from finding workarounds and increase my productivity tremendously.
Alternatively a flag on the package.json can also be an option, but I prefer the cli option, as it can be optionally added on cli npm start --compressed this way I can use it on the fly only when I need to and not always active/inactive.
Is your proposal related to a problem?
It's annoying having to deploy and check whether your improvements have worked or not, we can't get the localhost server to verify if lighthouse in devtools passes to a reasonable score.
Describe the solution you'd like
Whilst developing and fixing issues with lighthouse in devtools, it would be nice, on localhost we can provide an argument
npm run start --compress=trueso locahost serves compress gzipped CSS and JS etc.This will prevent me from finding workarounds and increase my productivity tremendously.
Alternatively a flag on the package.json can also be an option, but I prefer the cli option, as it can be optionally added on cli
npm start --compressedthis way I can use it on the fly only when I need to and not always active/inactive.