fix: measurementsAPI issue caused by production build (#842)

* ci: test docs-publish * Specify to use prod * Babel should transpile with env set by webpack * in-progress * in-progress * Polyfill for ie11 and edge features * Ditch polyfills w/ babel - we'll use a service for now * Bump tools version; shift vtk.js up a layer * Specify we shouldn't target older than IE 11 * ditch babel plugins that should be covered by preset-env * Add a top level build demo command * Let our babel config determine settings * Same babel fixes as PWA * Rebuild deps that don't satisfy our target * Mini helper script for excluding all node_modules, except... * Shift vtk.js dep up a layer * Kill core-js * Export in a node happy way * Updated yarn lock * Set NODE_ENV when launching anything w/ WebPack * docs: updated FAQ * docs: on browser support * Add support for redux browser extension * misc. small clean-up * docs: Remove roadmap page; add browser-support to sidebar * Formatting * Remove roadmap links * Formatting * ci: Remove config syntax error * Simplified bug report template * update community request template * Update question's template * simplify build scripts * specify new script names * fix: for measurement api being pruned by minimizer in prod builds * Use named exports * Simplify config * Let's not do so much heavy lifting for a dev-server build * fix dev build * Add hotkeys to demo * fix: jest babel config and env specific configs * Remove call to non-existant command * Shift experimental proposal plugin up a layer * Use `https` * Try with reduced number of package exceptions * Try to resolve cypress issue * Try to fix cypress issue in CI * Skip https
2019-09-04 13:53:13 -04:00
1 parent 25e7232660
commit 49d343941e
@@ -17,13 +17,7 @@ yarn add --dev -W package-name
  project
 - Remove all-contributors bot; install CLI per project and add per project
  commands
- Verify all have "dev:package-name" command
-  - Should we include `package.json` and `src` as output? (build from ESM)
-  - Should we remove `dev:package-name` commands and suggest navigating to
-    package root?
 - Fix broken peer dependencies?
- Lingering core-js resolution issues when building for Viewer PWA (from project
-  directory)

 ## ORBS

@@ -35,20 +29,6 @@ yarn add --dev -W package-name

 Debug Note: `http://localhost:3000/webpack-dev-server`

-NOTES:
-
-# bumps pre-release version of all packages if any changes
-
- `npx lerna version prerelease`
-
-# Releases based on package.json differences from NPM
-
- `npx lerna publish from-package --dist-tag canary`
-
-Use Env options to set config:
-
- https://webpack.js.org/api/cli/#environment-options
-
 ## Bundling

 - Extensions must bundle all assets into a single file for UMD