* 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
* Set node_env before building with WebPack
* Watch command output
* ci: no output timeout increase
* 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
* ci: test docs-publish
* Specify to use prod
* Babel should transpile with env set by webpack
* chore: production defaults to true; set in --env.production by cli
* Remove lingering merge issue
* Add minimification plugins
* Need relative URLs to find root assets
* Default public url to forward slash in define plugin
* Don't wrap w/ react-hot-loader if we're building for production
* No need to log extensions
* Minimize using terser; and minimize css
* Import redux from es; this bypasses commonjs as import and fixes our "production build" warning
* Split commone webpack build for now to test hotfix
* postfix slash
* undefined safe env access
* Try to fix node_env prod issue w/ redux
* Set NODE_ENV production for all prod builds
* Syntax error
* nix tests
* Increase max amount of available memory
* Don't run bundle analyzer by default
* fix: asset resolution when at non-root route
* ci: test docs-publish
* Specify to use prod
* Babel should transpile with env set by webpack
* chore: production defaults to true; set in --env.production by cli
* Remove lingering merge issue
* Add minimification plugins
* Need relative URLs to find root assets
* Default public url to forward slash in define plugin
* Don't wrap w/ react-hot-loader if we're building for production
* No need to log extensions
* Minimize using terser; and minimize css
* Import redux from es; this bypasses commonjs as import and fixes our "production build" warning
* Split commone webpack build for now to test hotfix
* postfix slash
* undefined safe env access
* Try to fix node_env prod issue w/ redux
* Set NODE_ENV production for all prod builds
* Syntax error
* nix tests
* Increase max amount of available memory
* Don't run bundle analyzer by default
* ci: test docs-publish
* Require unit tests for dry run
* ci: Make sure our docs publish is executable
* Try to correct path issue
* Try repo prefix
* Try as yarn command
* Need a workspace to attach to from previous step
* Add before we call our bash script
* See if we can enforce commands being available -- or just install locally?
* Try again
* Try SSH
* Include username in gh https url
* Note regarding failure on PR branches
* Remove docs publish from PR workflow
* chore: ability to specify an alternative html-template at build time
* chore: add command to build demo PWA website output
* chore: remove unused CI code
* Testing GCP capabilities
* syntax
* Naming
* naming
* chore: WebPack output progress that we care about
* chore: Only publish the app config we care about
* PWA should publish source map
* Unused index.html file
* chore: Remove unused copy-webpack-plugin ignore
* Don't generate source map until we resolve memory issue
* ci: attempt to publish with GCP bucket deploy
* Update dev config to use new template loccations and env vars
* ci: test docs-publish
* Require unit tests for dry run
* ci: Make sure our docs publish is executable
* Try to correct path issue
* Try repo prefix
* Try as yarn command
* Need a workspace to attach to from previous step
* Add before we call our bash script
* See if we can enforce commands being available -- or just install locally?
* Try again
* Try SSH
* Include username in gh https url
* Note regarding failure on PR branches
* Remove docs publish from PR workflow
* chore: ability to specify an alternative html-template at build time
* chore: add command to build demo PWA website output
* chore: remove unused CI code
* Testing GCP capabilities
* syntax
* Naming
* naming
* chore: WebPack output progress that we care about
* chore: Only publish the app config we care about
* PWA should publish source map
* Unused index.html file
* chore: Remove unused copy-webpack-plugin ignore
* Don't generate source map until we resolve memory issue
* ci: attempt to publish with GCP bucket deploy
* ci: test docs-publish
* Require unit tests for dry run
* ci: Make sure our docs publish is executable
* Try to correct path issue
* Try repo prefix
* Try as yarn command
* Need a workspace to attach to from previous step
* Add before we call our bash script
* See if we can enforce commands being available -- or just install locally?
* Try again
* Try SSH
* Include username in gh https url
* Note regarding failure on PR branches
* Remove docs publish from PR workflow
* chore: ability to specify an alternative html-template at build time
* chore: add command to build demo PWA website output
* chore: remove unused CI code
* Testing GCP capabilities
* syntax
* Naming
* naming
The props for ExpandableToolMenu were changed from expecting `text` to
expecting `label` for the menu's label. These changes make sure we're
providing it that way.
