* 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
64 lines
2.0 KiB
JavaScript
64 lines
2.0 KiB
JavaScript
const aliases = require('./aliases.config');
|
|
const path = require('path');
|
|
|
|
// https://babeljs.io/docs/en/options#babelrcroots
|
|
module.exports = {
|
|
babelrcRoots: ['./platform/*', './extensions/*'],
|
|
plugins: ['inline-react-svg', '@babel/plugin-proposal-class-properties'],
|
|
env: {
|
|
test: {
|
|
presets: [
|
|
[
|
|
// TODO: https://babeljs.io/blog/2019/03/19/7.4.0#migration-from-core-js-2
|
|
'@babel/preset-env',
|
|
{
|
|
modules: 'commonjs',
|
|
debug: false,
|
|
},
|
|
],
|
|
'@babel/preset-react',
|
|
],
|
|
plugins: [
|
|
'@babel/plugin-proposal-object-rest-spread',
|
|
'@babel/plugin-syntax-dynamic-import',
|
|
'@babel/plugin-transform-regenerator',
|
|
'@babel/plugin-transform-runtime',
|
|
],
|
|
},
|
|
production: {
|
|
presets: [
|
|
// WebPack handles ES6 --> Target Syntax
|
|
['@babel/preset-env', { modules: false }],
|
|
'@babel/preset-react',
|
|
],
|
|
ignore: ['**/*.test.jsx', '**/*.test.js', '__snapshots__', '__tests__'],
|
|
},
|
|
development: {
|
|
presets: [
|
|
// WebPack handles ES6 --> Target Syntax
|
|
['@babel/preset-env', { modules: false }],
|
|
'@babel/preset-react',
|
|
],
|
|
plugins: ['react-hot-loader/babel'],
|
|
ignore: ['**/*.test.jsx', '**/*.test.js', '__snapshots__', '__tests__'],
|
|
},
|
|
},
|
|
};
|
|
|
|
// TODO: Plugins; Aliases
|
|
// We don't currently use aliases, but this is a nice snippet that would help
|
|
// [
|
|
// 'module-resolver',
|
|
// {
|
|
// // https://github.com/tleunen/babel-plugin-module-resolver/issues/338
|
|
// // There seem to be a bug with module-resolver with a mono-repo setup:
|
|
// // It doesn't resolve paths correctly when using root/alias combo, so we
|
|
// // use this function instead.
|
|
// resolvePath(sourcePath, currentFile, opts) {
|
|
// // This will return undefined if aliases has no key for the sourcePath,
|
|
// // in which case module-resolver will fallback on its default behaviour.
|
|
// return aliases[sourcePath];
|
|
// },
|
|
// },
|
|
// ],
|