Browse files

packager: add basic top-level integration test

Summary: I'd like us to start having some decent testing at the packager/bundler level to check that there are no major breakage hapenning. This changeset introduce a simple test that just test the `buildBundle` public API. On the same model, I'd like to test the server API and behavior, and things such as hot module reloading. I hope this will also highlight the gross inconsistencies of the API, for example the Bundle/BundleBase hierarchy, that we can proceed to fix later.

Reviewed By: davidaurelio, cpojer

Differential Revision: D5121817

fbshipit-source-id: e0f3758c7fbb7a85cf51fb3cbc34c12d5374b7d3
  • Loading branch information...
jeanlauliac authored and facebook-github-bot committed May 26, 2017
1 parent e40d1a1 commit 32d35c31f7fa4c0b64e8a4f2c70647072176e2e4
@@ -54,6 +54,8 @@ type PublicBundleOptions = {
+sourceMapUrl?: string,
exports.TransformCaching = TransformCaching;
* This is a public API, so we don't trust the value and purposefully downgrade
* it as `mixed`. Because it understands `invariant`, Flow ensure that we
Oops, something went wrong.

0 comments on commit 32d35c3

Please sign in to comment.