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
facebook · May 26, 2017 · 32d35c3 · 32d35c3
1 parent e40d1a1
commit 32d35c3
Show file tree

Hide file tree

Showing 7 changed files with 1,382 additions and 0 deletions.
diff --git a/packager/index.js b/packager/index.js
@@ -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