-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
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
Add app in top level config #7
Conversation
steventsao
commented
Mar 14, 2019
- updated readme
- updated tests to handle the new config
Resolves #2. |
- updated readme - updated tests to handle the new config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @steventsao, this looks very good!
This is a breaking change, as any old (flat) config would not work with the new approach, right?
I guess you could provide an upgrade path, by supporting both formats and deprecating the previous one. But tbh, I am not that much worried about it, we can certainly just bump the minor version and tell users how to upgrade...
What I am really surprised about is that the blueprint test is not failing! It seems you (rightly) changed the default blueprint, but forgot to update the test fixture (https://github.com/kaliber5/ember-cli-bundlesize/blob/master/node-tests/fixtures/config/bundlesize.js). No big deal, but I really don't understand why this was not failing the test!? 🤔
It looks like the test only passed because |
Seems you are right, thanks for investigating!
I prefer not to compare buffers, but still use the |
Done. the error case looks much better than using buffer.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks awesome, thank you!
Published as 0.1.0! 🎉 |