mirror of
https://github.com/embarklabs/embark.git
synced 2025-01-12 14:54:57 +00:00
7a93e4b6a7
TL;DR ===== `yarn install` in a fresh clone of the repo. `yarn reboot` when switching branches. When pulling in these changes, there may be untracked files at the root in all/some of: ``` .embark/ .nyc_output/ coverage/ dist/ embark-ui/ test_apps/ ``` They can be safely deleted since those paths are no longer in use at the root. Many of the scripts in the top-level `package.json` support Lerna's [filter options]. For example: `yarn build --scope embark` build only `packages/embark`. `yarn build --ignore embark-ui` build everything except `packages/embark-ui`. Scoping scripts will be more useful when there are more packages in the monorepo and, for example, `yarn start` doesn't need to be invoked for all of them while working on just a few of them simultaneously, e.g `embark` and `embarkjs`. It's also possible to `cd` into a particular package and run its scripts directly: ``` cd packages/embark && yarn watch ``` Hot Topics & Questions ====================== What should be done about the [README][embark-readme] for `packages/embark`? Should the top-level README be duplicated in that package? Lerna is setup to use [Fixed/Locked mode][fixed-locked], and accordingly `packages/embark-ui` is set to `4.0.0-beta.0`. The same will be true when adding embarkjs, swarm-api, etc. to the monorepo. Is this acceptable or do we want to use [Independent mode][independent]? Scripts ======= If a package doesn't have a matching script, `lerna run` skips it automatically. For example, `packages/embark-ui` doesn't have a `typecheck` script. `yarn build` ------------ Runs babel, webpack, etc. according to a package's `build` script. `yarn build:no-ui` is a shortcut for `yarn build --ignore embark-ui`. `yarn ci` --------- Runs a series of scripts relevant in a CI context according to a package's `ci` script. For `packages/embark` that's `lint typecheck build test package`. Also runs the `ci` script of the embedded `test_dapps` monorepo. `yarn clean` ------------ Runs rimraf, etc. according to a package's `clean` script. `yarn globalize` ---------------- Makes the development embark available on the global PATH, either via symlink (Linux, macOS) or a shim script (Windows). `yarn lint` ----------- Runs eslint, etc. according to a package's `lint` script. `yarn package` -------------- Invokes `npm pack` according to a package's `package` script. `yarn qa` --------- Very similar to `ci`, runs a series of scripts according to a package's `qa` script. The big difference between `ci` and `qa` is that at the top-level `qa` first kicks off `reboot:full`. There is a `preqa` script ([invoked automatically][npm-scripts]), which is a bit of a wart. It makes sure that `embark reset` can be run successfully in `packages/embark/templates/*` when the `reboot` script invokes the `reset` script. The `qa` script is invoked by `yarn release` before the latter proceeds to invoke `lerna publish`. `yarn reboot` ------------- Invokes the `reset` script and then does `yarn install`. The `reboot:full` variant invokes `reset:full` and then does `yarn install`. `yarn release` -------------- Works in concert with [lerna publish], which will prompt to verify the version before proceeding. Use `n` to cancel instead of `ctrl-c` as `lerna publish` has been seen to occasionally misbehave when not exited cleanly (e.g. creating a tag when it shouldn't have). ``` yarn release [bump] [--options] ``` * `[bump]` see [`publish` positionals][pub-pos] and [`version` positionals][ver-pos]; an exact version can also be specified. * `--preid` prerelease identifier, e.g. `beta`; when doing a prerelease bump will default to whatever identifier is currently in use. * `--dist-tag` registry distribution tag, defaults to `latest`. * `--message` commit message format, defaults to `chore(release): %v`. * `--sign` indicates that the git commit and tag should be signed; not signed by default. * `--release-branch` default is `master`; must match the current branch. * `--git-remote` default is `origin`. * `--registry` default is `https://registry.npmjs.org/` per the top-level [`lerna.json`][lerna-json]. To release `4.0.0-beta.1` as `embark@next` (assuming version is currently at `4.0.0-beta.0`) could do: ``` yarn release prerelease --dist-tag next ``` For *test releases* (there is no longer a `--dry-run` option) [verdaccio] and a filesystem git remote can be used. Condensend instructions: ``` mkdir -p ~/temp/clones && cd ~/temp/clones git clone git@github.com:embark-framework/embark.git cd ~/repos/embark git remote add FAKEembark ~/temp/clones/embark ``` in another terminal: ``` npm i -g verdaccio && verdaccio ``` in the first terminal: ``` yarn release --git-remote FAKEembark --registry http://localhost:4873/ ``` `yarn reset` ------------ Invokes cleaning and resetting steps according to a package's `reset` script. The big difference between `clean` and `reset` is that `reset` is intended to delete a package's `node_modules`. The `reset:full` variant deletes the monorepo's top-level `node_modules` at the end. That shouldn't be necessary too often, e.g. in day-to-day work when switching branches, which is why there is `reboot` / `reset` vs. `reboot:full` / `reset:full`. Errors may be seen related to invocation of `embark reset` if embark is not built, but `reset` will still complete successfully. `yarn start` ------------ Runs babel, webpack, tsc, etc. (in parallel, in watch mode) according to a package's `start` script. `yarn test` ----------- Run mocha, etc. according to a package's `test` script. The `test:full` variant runs a series of scripts: `lint typecheck test test_dapps`. `yarn test_dapps` ----------------- Runs the `test` script of the embedded `test_dapps` monorepo. The `test_dapps:ci` and `test_dapps:qa` variants run the `ci` and `qa` scripts of the embedded `test_dapps` monorepo, respectively. `yarn typecheck` ---------------- Runs tsc, etc. according to a package's `typecheck` script. Notes ===== `npx` is used in some of the top-level and package scripts to ensure the scripts can run even if `node_modules` is missing. [`"nohoist"`][nohoist] specifies a couple of embark packages because [`restrictPath`][restrictpath] is interfering with access to modules that are located in a higher-up `node_modules`. All dependencies in `packages/embark-ui` have been made `devDependencies` since its production build is self-contained. `packages/embark`'s existing CHANGELOG's formatting has been slightly adjusted to match the formatting that Lerna will use going forward (entries in the log haven't been modified). Lerna will generate a CHANGELOG at the top-level and in each package. Since we're transitioning to a monorepo, things may look a little wonky with respect to old entries in `packages/embark/CHANGELOG.md` and going forward we need to consider how scoping our commits corresponds to member-packages of the monorepo. In `packages/embark`, `test` invokes `scripts/test`, which starts a child process wherein `process.env.DAPP_PATH` is a temporary path that has all of `packages/embark/dist/test` copied into it, so that paths to test helpers/fixtures don't need to be prefixed with `dist/test/` and so that a `.embark` directory doesn't get written into `packages/embark`. The `"engines"` specified in top-level and packages' `package.json` reflect a node and npm pair that match (a source of confusion in the past). The pair was chosen according to the first post v5 npm that's bundled with node. A `"runtime"` key/object has been introduced in `packages/embark/package.json` which is used as the basis for specifying the minimum version of node that can be used to run embark, and that's what is checked by `bin/embark`. Some changes have been introduced, e.g. in `lib/core/config` and `lib/utils/solidity/remapImports` so that it's *not* implicitly assumed that `process.env.DAPP_PATH` / `fs.dappPath()` are the same as `process.cwd()`. There are probably several++ places where that assumption is still in effect, and we should work to identify and correct them. `embark reset` now deletes `embarkArtifacts/` within a dapp root, and `embarkArtifacts/` is git-ignored. `lib/core/env` adds all `node_modules` relative to `process.env.EMBARK_PATH` to `NODE_PATH` so that embark's modules can be resolved as expected whether embark's `node_modules` have been deduped or are installed in npm's flat "global style". `checkDependencies` has been inlined (see `lib/utils/checkDependencies`) and slightly modified to support dependencies that have been hoisted into a higher-up `node_modules`, e.g. as part of a yarn workspace. eslint has been disabled for that script to avoid more involved changes to it. `test_apps` is not in `packages/embark`; rather, there is `test_dapps` at the top-level of the monorepo. `test_dapps` is an embedded monorepo, and its `ci` / `qa` scripts `npm install` embark from freshly built tarballs of the packages in the outer monorepo and then use that installation to run `embark test` in the dapps. This should allow us to rapidly detect breakage related to auto-bumps in transitive dependencies. [filter options]: https://github.com/lerna/lerna/tree/master/core/filter-options [embark-readme]: https://github.com/embark-framework/embark/blob/build/lerna/packages/embark/README.md [fixed-locked]: https://github.com/lerna/lerna#fixedlocked-mode-default [independent]: https://github.com/lerna/lerna#independent-mode [npm-scripts]: https://docs.npmjs.com/misc/scripts [lerna publish]: https://github.com/lerna/lerna/tree/master/commands/publish [pub-pos]: https://github.com/lerna/lerna/tree/master/commands/publish#positionals [ver-pos]: https://github.com/lerna/lerna/tree/master/commands/version#positionals [lerna-json]: https://github.com/embark-framework/embark/blob/build/lerna/lerna.json#L11 [verdaccio]: https://www.npmjs.com/package/verdaccio [nohoist]: https://github.com/embark-framework/embark/blob/build/lerna/package.json#L52-L55 [restrictpath]: https://github.com/embark-framework/embark/blob/build/lerna/packages/embark/src/lib/core/fs.js#L9
424 lines
18 KiB
JavaScript
424 lines
18 KiB
JavaScript
const fs = require('fs');
|
|
const path = require('path');
|
|
const resolve = require('resolve');
|
|
const webpack = require('webpack');
|
|
const PnpWebpackPlugin = require('pnp-webpack-plugin');
|
|
const HtmlWebpackPlugin = require('html-webpack-plugin');
|
|
const CaseSensitivePathsPlugin = require('case-sensitive-paths-webpack-plugin');
|
|
const InterpolateHtmlPlugin = require('react-dev-utils/InterpolateHtmlPlugin');
|
|
const WatchMissingNodeModulesPlugin = require('react-dev-utils/WatchMissingNodeModulesPlugin');
|
|
const ModuleScopePlugin = require('react-dev-utils/ModuleScopePlugin');
|
|
const getCSSModuleLocalIdent = require('react-dev-utils/getCSSModuleLocalIdent');
|
|
const getClientEnvironment = require('./env');
|
|
const paths = require('./paths');
|
|
const ManifestPlugin = require('webpack-manifest-plugin');
|
|
const ModuleNotFoundPlugin = require('react-dev-utils/ModuleNotFoundPlugin');
|
|
const ForkTsCheckerWebpackPlugin = require('fork-ts-checker-webpack-plugin-alt');
|
|
const typescriptFormatter = require('react-dev-utils/typescriptFormatter');
|
|
|
|
const MonacoWebpackPlugin = require('monaco-editor-webpack-plugin');
|
|
|
|
// Webpack uses `publicPath` to determine where the app is being served from.
|
|
// In development, we always serve from the root. This makes config easier.
|
|
const publicPath = '/';
|
|
// `publicUrl` is just like `publicPath`, but we will provide it to our app
|
|
// as %PUBLIC_URL% in `index.html` and `process.env.PUBLIC_URL` in JavaScript.
|
|
// Omit trailing slash as %PUBLIC_PATH%/xyz looks better than %PUBLIC_PATH%xyz.
|
|
const publicUrl = '';
|
|
// Get environment variables to inject into our app.
|
|
const env = getClientEnvironment(publicUrl);
|
|
|
|
// Check if TypeScript is setup
|
|
const useTypeScript = fs.existsSync(paths.appTsConfig);
|
|
|
|
// style files regexes
|
|
const cssRegex = /\.css$/;
|
|
const cssModuleRegex = /\.module\.css$/;
|
|
const sassRegex = /\.(scss|sass)$/;
|
|
const sassModuleRegex = /\.module\.(scss|sass)$/;
|
|
|
|
// common function to get style loaders
|
|
const getStyleLoaders = (cssOptions, preProcessor) => {
|
|
const loaders = [
|
|
require.resolve('style-loader'),
|
|
{
|
|
loader: require.resolve('css-loader'),
|
|
options: cssOptions,
|
|
},
|
|
{
|
|
// Options for PostCSS as we reference these options twice
|
|
// Adds vendor prefixing based on your specified browser support in
|
|
// package.json
|
|
loader: require.resolve('postcss-loader'),
|
|
options: {
|
|
// Necessary for external CSS imports to work
|
|
// https://github.com/facebook/create-react-app/issues/2677
|
|
ident: 'postcss',
|
|
plugins: () => [
|
|
require('postcss-flexbugs-fixes'),
|
|
require('postcss-preset-env')({
|
|
autoprefixer: {
|
|
flexbox: 'no-2009',
|
|
},
|
|
stage: 3,
|
|
}),
|
|
],
|
|
},
|
|
},
|
|
];
|
|
if (preProcessor) {
|
|
loaders.push(require.resolve(preProcessor));
|
|
}
|
|
return loaders;
|
|
};
|
|
|
|
// This is the development configuration.
|
|
// It is focused on developer experience and fast rebuilds.
|
|
// The production configuration is different and lives in a separate file.
|
|
module.exports = {
|
|
mode: 'development',
|
|
// You may want 'eval' instead if you prefer to see the compiled output in DevTools.
|
|
// See the discussion in https://github.com/facebook/create-react-app/issues/343
|
|
devtool: 'cheap-module-source-map',
|
|
// These are the "entry points" to our application.
|
|
// This means they will be the "root" imports that are included in JS bundle.
|
|
entry: [
|
|
// Include an alternative client for WebpackDevServer. A client's job is to
|
|
// connect to WebpackDevServer by a socket and get notified about changes.
|
|
// When you save a file, the client will either apply hot updates (in case
|
|
// of CSS changes), or refresh the page (in case of JS changes). When you
|
|
// make a syntax error, this client will display a syntax error overlay.
|
|
// Note: instead of the default WebpackDevServer client, we use a custom one
|
|
// to bring better experience for Create React App users. You can replace
|
|
// the line below with these two lines if you prefer the stock client:
|
|
// require.resolve('webpack-dev-server/client') + '?/',
|
|
// require.resolve('webpack/hot/dev-server'),
|
|
require.resolve('react-dev-utils/webpackHotDevClient'),
|
|
// Finally, this is your app's code:
|
|
paths.appIndexJs,
|
|
// We include the app code last so that if there is a runtime error during
|
|
// initialization, it doesn't blow up the WebpackDevServer client, and
|
|
// changing JS code would still trigger a refresh.
|
|
],
|
|
output: {
|
|
// Add /* filename */ comments to generated require()s in the output.
|
|
pathinfo: true,
|
|
// This does not produce a real file. It's just the virtual path that is
|
|
// served by WebpackDevServer in development. This is the JS bundle
|
|
// containing code from all our entry points, and the Webpack runtime.
|
|
filename: 'static/js/bundle.js',
|
|
// There are also additional JS chunk files if you use code splitting.
|
|
chunkFilename: 'static/js/[name].chunk.js',
|
|
// This is the URL that app is served from. We use "/" in development.
|
|
publicPath: publicPath,
|
|
// Point sourcemap entries to original disk location (format as URL on Windows)
|
|
devtoolModuleFilenameTemplate: info =>
|
|
path.resolve(info.absoluteResourcePath).replace(/\\/g, '/'),
|
|
},
|
|
optimization: {
|
|
// Automatically split vendor and commons
|
|
// https://twitter.com/wSokra/status/969633336732905474
|
|
// https://medium.com/webpack/webpack-4-code-splitting-chunk-graph-and-the-splitchunks-optimization-be739a861366
|
|
splitChunks: {
|
|
chunks: 'all',
|
|
name: false,
|
|
},
|
|
// Keep the runtime chunk seperated to enable long term caching
|
|
// https://twitter.com/wSokra/status/969679223278505985
|
|
runtimeChunk: true,
|
|
},
|
|
resolve: {
|
|
// This allows you to set a fallback for where Webpack should look for modules.
|
|
// We placed these paths second because we want `node_modules` to "win"
|
|
// if there are any conflicts. This matches Node resolution mechanism.
|
|
// https://github.com/facebook/create-react-app/issues/253
|
|
modules: ['node_modules'].concat(
|
|
// It is guaranteed to exist because we tweak it in `env.js`
|
|
process.env.NODE_PATH.split(path.delimiter).filter(Boolean)
|
|
),
|
|
// These are the reasonable defaults supported by the Node ecosystem.
|
|
// We also include JSX as a common component filename extension to support
|
|
// some tools, although we do not recommend using it, see:
|
|
// https://github.com/facebook/create-react-app/issues/290
|
|
// `web` extension prefixes have been added for better support
|
|
// for React Native Web.
|
|
extensions: paths.moduleFileExtensions
|
|
.map(ext => `.${ext}`)
|
|
.filter(ext => useTypeScript || !ext.includes('ts')),
|
|
alias: {
|
|
// Support React Native Web
|
|
// https://www.smashingmagazine.com/2016/08/a-glimpse-into-the-future-with-react-native-for-web/
|
|
'react-native': 'react-native-web',
|
|
},
|
|
plugins: [
|
|
// Adds support for installing with Plug'n'Play, leading to faster installs and adding
|
|
// guards against forgotten dependencies and such.
|
|
PnpWebpackPlugin,
|
|
// Prevents users from importing files from outside of src/ (or node_modules/).
|
|
// This often causes confusion because we only process files within src/ with babel.
|
|
// To fix this, we prevent you from importing files out of src/ -- if you'd like to,
|
|
// please link the files into your node_modules/ and let module-resolution kick in.
|
|
// Make sure your source files are compiled, as they will not be processed in any way.
|
|
new ModuleScopePlugin(paths.appSrc, [paths.appPackageJson]),
|
|
],
|
|
},
|
|
resolveLoader: {
|
|
plugins: [
|
|
// Also related to Plug'n'Play, but this time it tells Webpack to load its loaders
|
|
// from the current package.
|
|
PnpWebpackPlugin.moduleLoader(module),
|
|
],
|
|
},
|
|
module: {
|
|
strictExportPresence: true,
|
|
rules: [
|
|
// Disable require.ensure as it's not a standard language feature.
|
|
{ parser: { requireEnsure: false } },
|
|
|
|
// First, run the linter.
|
|
// It's important to do this before Babel processes the JS.
|
|
{
|
|
test: /\.(js|mjs|jsx)$/,
|
|
enforce: 'pre',
|
|
use: [
|
|
{
|
|
options: {
|
|
formatter: require.resolve('react-dev-utils/eslintFormatter'),
|
|
eslintPath: require.resolve('eslint'),
|
|
|
|
},
|
|
loader: require.resolve('eslint-loader'),
|
|
},
|
|
],
|
|
include: paths.appSrc,
|
|
},
|
|
{
|
|
// "oneOf" will traverse all following loaders until one will
|
|
// match the requirements. When no loader matches it will fall
|
|
// back to the "file" loader at the end of the loader list.
|
|
oneOf: [
|
|
// "url" loader works like "file" loader except that it embeds assets
|
|
// smaller than specified limit in bytes as data URLs to avoid requests.
|
|
// A missing `test` is equivalent to a match.
|
|
{
|
|
test: [/\.bmp$/, /\.gif$/, /\.jpe?g$/, /\.png$/],
|
|
loader: require.resolve('url-loader'),
|
|
options: {
|
|
limit: 10000,
|
|
name: 'static/media/[name].[hash:8].[ext]',
|
|
},
|
|
},
|
|
// Process application JS with Babel.
|
|
// The preset includes JSX, Flow, and some ESnext features.
|
|
{
|
|
test: /\.(js|mjs|jsx|ts|tsx)$/,
|
|
include: paths.appSrc,
|
|
loader: require.resolve('babel-loader'),
|
|
options: {
|
|
customize: require.resolve(
|
|
'babel-preset-react-app/webpack-overrides'
|
|
),
|
|
|
|
plugins: [
|
|
[
|
|
require.resolve('babel-plugin-named-asset-import'),
|
|
{
|
|
loaderMap: {
|
|
svg: {
|
|
ReactComponent: '@svgr/webpack?-prettier,-svgo![path]',
|
|
},
|
|
},
|
|
},
|
|
],
|
|
],
|
|
// This is a feature of `babel-loader` for webpack (not Babel itself).
|
|
// It enables caching results in ./node_modules/.cache/babel-loader/
|
|
// directory for faster rebuilds.
|
|
cacheDirectory: true,
|
|
// Don't waste time on Gzipping the cache
|
|
cacheCompression: false,
|
|
},
|
|
},
|
|
// Process any JS outside of the app with Babel.
|
|
// Unlike the application JS, we only compile the standard ES features.
|
|
{
|
|
test: /\.(js|mjs)$/,
|
|
exclude: /@babel(?:\/|\\{1,2})runtime/,
|
|
loader: require.resolve('babel-loader'),
|
|
options: {
|
|
babelrc: false,
|
|
configFile: false,
|
|
compact: false,
|
|
presets: [
|
|
[
|
|
require.resolve('babel-preset-react-app/dependencies'),
|
|
{ helpers: true },
|
|
],
|
|
],
|
|
cacheDirectory: true,
|
|
// Don't waste time on Gzipping the cache
|
|
cacheCompression: false,
|
|
|
|
// If an error happens in a package, it's possible to be
|
|
// because it was compiled. Thus, we don't want the browser
|
|
// debugger to show the original code. Instead, the code
|
|
// being evaluated would be much more helpful.
|
|
sourceMaps: false,
|
|
},
|
|
},
|
|
// "postcss" loader applies autoprefixer to our CSS.
|
|
// "css" loader resolves paths in CSS and adds assets as dependencies.
|
|
// "style" loader turns CSS into JS modules that inject <style> tags.
|
|
// In production, we use a plugin to extract that CSS to a file, but
|
|
// in development "style" loader enables hot editing of CSS.
|
|
// By default we support CSS Modules with the extension .module.css
|
|
{
|
|
test: cssRegex,
|
|
exclude: cssModuleRegex,
|
|
use: getStyleLoaders({
|
|
importLoaders: 1,
|
|
}),
|
|
},
|
|
// Adds support for CSS Modules (https://github.com/css-modules/css-modules)
|
|
// using the extension .module.css
|
|
{
|
|
test: cssModuleRegex,
|
|
use: getStyleLoaders({
|
|
importLoaders: 1,
|
|
modules: true,
|
|
getLocalIdent: getCSSModuleLocalIdent,
|
|
}),
|
|
},
|
|
// Opt-in support for SASS (using .scss or .sass extensions).
|
|
// Chains the sass-loader with the css-loader and the style-loader
|
|
// to immediately apply all styles to the DOM.
|
|
// By default we support SASS Modules with the
|
|
// extensions .module.scss or .module.sass
|
|
{
|
|
test: sassRegex,
|
|
exclude: sassModuleRegex,
|
|
use: getStyleLoaders({ importLoaders: 2 }, 'sass-loader'),
|
|
},
|
|
// Adds support for CSS Modules, but using SASS
|
|
// using the extension .module.scss or .module.sass
|
|
{
|
|
test: sassModuleRegex,
|
|
use: getStyleLoaders(
|
|
{
|
|
importLoaders: 2,
|
|
modules: true,
|
|
getLocalIdent: getCSSModuleLocalIdent,
|
|
},
|
|
'sass-loader'
|
|
),
|
|
},
|
|
// "file" loader makes sure those assets get served by WebpackDevServer.
|
|
// When you `import` an asset, you get its (virtual) filename.
|
|
// In production, they would get copied to the `build` folder.
|
|
// This loader doesn't use a "test" so it will catch all modules
|
|
// that fall through the other loaders.
|
|
{
|
|
// Exclude `js` files to keep "css" loader working as it injects
|
|
// its runtime that would otherwise be processed through "file" loader.
|
|
// Also exclude `html` and `json` extensions so they get processed
|
|
// by webpacks internal loaders.
|
|
exclude: [/\.(js|mjs|jsx|ts|tsx)$/, /\.html$/, /\.json$/],
|
|
loader: require.resolve('file-loader'),
|
|
options: {
|
|
name: 'static/media/[name].[hash:8].[ext]',
|
|
},
|
|
},
|
|
],
|
|
},
|
|
// ** STOP ** Are you adding a new loader?
|
|
// Make sure to add the new loader(s) before the "file" loader.
|
|
],
|
|
},
|
|
plugins: [
|
|
// Generates an `index.html` file with the <script> injected.
|
|
new HtmlWebpackPlugin({
|
|
inject: true,
|
|
template: paths.appHtml,
|
|
}),
|
|
// Makes some environment variables available in index.html.
|
|
// The public URL is available as %PUBLIC_URL% in index.html, e.g.:
|
|
// <link rel="shortcut icon" href="%PUBLIC_URL%/favicon.ico">
|
|
// In development, this will be an empty string.
|
|
new InterpolateHtmlPlugin(HtmlWebpackPlugin, env.raw),
|
|
// This gives some necessary context to module not found errors, such as
|
|
// the requesting resource.
|
|
new ModuleNotFoundPlugin(paths.appPath),
|
|
// Makes some environment variables available to the JS code, for example:
|
|
// if (process.env.NODE_ENV === 'development') { ... }. See `./env.js`.
|
|
new webpack.DefinePlugin(env.stringified),
|
|
// This is necessary to emit hot updates (currently CSS only):
|
|
new webpack.HotModuleReplacementPlugin(),
|
|
// Watcher doesn't work well if you mistype casing in a path so we use
|
|
// a plugin that prints an error when you attempt to do this.
|
|
// See https://github.com/facebook/create-react-app/issues/240
|
|
new CaseSensitivePathsPlugin(),
|
|
// If you require a missing module and then `npm install` it, you still have
|
|
// to restart the development server for Webpack to discover it. This plugin
|
|
// makes the discovery automatic so you don't have to restart.
|
|
// See https://github.com/facebook/create-react-app/issues/186
|
|
new WatchMissingNodeModulesPlugin(paths.appNodeModules),
|
|
// Moment.js is an extremely popular library that bundles large locale files
|
|
// by default due to how Webpack interprets its code. This is a practical
|
|
// solution that requires the user to opt into importing specific locales.
|
|
// https://github.com/jmblog/how-to-optimize-momentjs-with-webpack
|
|
// You can remove this if you don't use Moment.js:
|
|
new webpack.IgnorePlugin(/^\.\/locale$/, /moment$/),
|
|
// Generate a manifest file which contains a mapping of all asset filenames
|
|
// to their corresponding output file so that tools can pick it up without
|
|
// having to parse `index.html`.
|
|
new ManifestPlugin({
|
|
fileName: 'asset-manifest.json',
|
|
publicPath: publicPath,
|
|
}),
|
|
// TypeScript type checking
|
|
useTypeScript &&
|
|
new ForkTsCheckerWebpackPlugin({
|
|
typescript: resolve.sync('typescript', {
|
|
basedir: paths.appNodeModules,
|
|
}),
|
|
async: false,
|
|
checkSyntacticErrors: true,
|
|
tsconfig: paths.appTsConfig,
|
|
compilerOptions: {
|
|
module: 'esnext',
|
|
moduleResolution: 'node',
|
|
resolveJsonModule: true,
|
|
isolatedModules: true,
|
|
noEmit: true,
|
|
jsx: 'preserve',
|
|
},
|
|
reportFiles: [
|
|
'**',
|
|
'!**/*.json',
|
|
'!**/__tests__/**',
|
|
'!**/?(*.)(spec|test).*',
|
|
'!src/setupProxy.js',
|
|
'!src/setupTests.*',
|
|
],
|
|
watch: paths.appSrc,
|
|
silent: true,
|
|
formatter: typescriptFormatter,
|
|
}),
|
|
|
|
new MonacoWebpackPlugin(),
|
|
].filter(Boolean),
|
|
|
|
// Some libraries import Node modules but don't use them in the browser.
|
|
// Tell Webpack to provide empty mocks for them so importing them works.
|
|
node: {
|
|
dgram: 'empty',
|
|
fs: 'empty',
|
|
net: 'empty',
|
|
tls: 'empty',
|
|
child_process: 'empty',
|
|
},
|
|
// Turn off performance processing because we utilize
|
|
// our own hints via the FileSizeReporter
|
|
performance: false,
|
|
};
|