Remove the `include` setting from webpack loaders for CSS, JSON and other static assets.
This way it's possible to import files from a separate config folder, a parent directory etc.
This rule is considered dangerous in certain situations. This is especially true for Immutable.js users. See the discussion at issue #465 for more information about this.
* Load favicon through html-loader.
Fixes#291.
* Add test for *.ico in e2e test suite
* Configure html-loader to process <link href="...">
* Address feedback on html-loader inclusion.
* Place favicon.ico at the root of the build dir
* Make comment style consistent between prod and dev webpack configs
* Fix html-loader config in dev mode
* Transform async functions with regenerator
Remove `transform-async-to-generator`, which to my understanding is meant
to be used in environments that support generators natively.
Because we're compiling generators to ES5 anyway, we can simply use
`regenerator` to transform async functions too, which results in
slightly simpler output and only uses the regenerator runtime instead
regenerator runtime + _asyncToGenerator Babel helper.
* Add babel-plugin-transform-regenerator
* Use dependencies with an exact version
* Symlink-friendly path resolution
I was having difficulties using a local copy of `react-scripts` and `npm link`ing it into a real world project. This change resolves paths relative to the current working directory (that is, most likely the directory of the app) rather than assuming a certain directory structure.
* Fix relative paths in post-eject case
because I'm an idiot
* Renamed resolveLib to resolveOwn
* Use keyword `warn` in eslint config
We can use the keyword `warn` for rule configuration instead of a number.
* Fix comment which where WARNING was replaced
* Remove extra apostrophe
This project is a really good use case to apply some accessibility
rules to the lint config. For beginners getting started with React, we
can also teach/enforce basic accessibility rules in the web at author
time.
For now, I’ve just applied to the rules that are listed in
`eslint-config-airbnb` because these are most real-world tested, and we
can continue to add.
Happy to help if there are any questions/issues/concerns about the
plugin!
* Don't assume the project is hosted at the root
* Require package.json in webpack.config.prod.js and use homepage if set; otherwise use '/'
* Fix package.json path and add sample package.json for tests
* Update publicPath to use relative path portion of URL defined in homepage
* Update successful bundle generation message
* Show bundle generation success message based on presence of homepage in package.json
