3216f5596e
Summary: The version number displayed in the application now displays much more specific information. It now lists the Git commit from which the build was constructed, and will identify whether we have accidentally deployed a development instance (which would be slow) or an instance with uncommitted changes (which would be bad). The version information is computed during the initialization of the Webpack config. For development, this means that it is computed when you run `yarn start`, and not updated thenafter. If the stale information presents actual confusion, we would need to backport Webpack 4’s support for runtime values in `DefinePlugin` to Webpack 3 (or upgrade Webpack by a major version). Test Plan: The logic for `GitState` and `Environment` has existing tests. With both a clean tree and a dirty tree, run `yarn start` and build the static site, and check that the resulting versions are correct. wchargin-branch: use-rich-version-types |
||
|---|---|---|
| .. | ||
| jest | ||
| RemoveBuildDirectoryPlugin.js | ||
| babel.js | ||
| env.js | ||
| makeWebpackConfig.js | ||
| paths.js | ||
| polyfills.js | ||
| test.js | ||
| webpack.config.backend.js | ||