Allow bundlesize to be configured by a file rather than relying on package.json #206
Labels
Milestone
Comments
|
I would love this feature too. This should be fairly easy to achieve with this package https://github.com/davidtheclark/cosmiconfig. It is for instance used in |
|
Related to: #162 |
wmfgerrit
pushed a commit
to wikimedia/mediawiki-extensions-MobileFrontend
that referenced
this issue
Aug 30, 2018
This patch adds a production build output gzipped file size check to the test script so that any future changes may only introduce known size differences. Note: • The initial limit was taken from the present gzipped file size rounded up to the 10th of a kibibyte. • JEDEC notation is used. bundlesize internally uses Bytes utility which only supports base 2 units. https://github.com/visionmedia/bytes.js • The bundlesize config cannot yet be stored in a distinct file. siddharthkp/bundlesize#206 Bug: T202742 Bug: T199452 Change-Id: Ic7766f16918db47371e081bf6542e133544d7d0d
Open
|
Implemented in #316 and published in 0.18.0 🎉 Check out README for details |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
Configuration can only be read from package.json file
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
To be able to pass in configuration by specifying path to a file.
For example:
$ bundlesize --config ./configs/bundlesize/config.jsonIf this is a feature request, what is motivation or use case for changing the behavior?
Avoid cluttering up package.json
Please mention other relevant information.
The text was updated successfully, but these errors were encountered: