We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Probably would be a great improvement to have and option to load different configuration files either from npm run size or from cli
npm run size
Just like .dotenv file you could have .size-limit which will always be the default one and eventually .size-limit.prod
.dotenv
.size-limit
.size-limit.prod
The text was updated successfully, but these errors were encountered:
Hm. Why do you need different environment? Maybe there is a more simple way.
Sorry, something went wrong.
If you're just looking for cli options you can just disable the internal webpack and manually run your own webpack build.
For example, you can try adding this within your package.json
package.json
"scripts": { "build": "webpack --config your-custom-config-file.js dist/output.js", "size": "npm run build && size-limit" }, "size-limit": [ { "limit": "300 KB", "webpack": false, "path": "dist/output.js" } ]
Now, npm run size will just run with whatever configuration files you provide.
All config options are available by CLI option. So if you want to have different configs:
size-limit 10 KB app.js --no-webpack
I think CLI options will be enough.
But I will open this feature request again when somebody will show me use case for different configs.
No branches or pull requests
Probably would be a great improvement to have and option to load different configuration files either from
npm run size
or from cliJust like
.dotenv
file you could have.size-limit
which will always be the default one and eventually.size-limit.prod
The text was updated successfully, but these errors were encountered: