* Add named asset import for svg files via babel plugin and webpack loader.
* Fix failing e2e test
* Switched to svgr loader
* Updated SVG component test
* Disable named asset import plugin in test environment
* Added tests for including SVG in CSS
* Update tests
* Moved babel plugin config into webpack config
* Support for multiple source paths via package.json srcPaths entry.
Initial support for yarn workspace.
Support lerna workspace, fix for when to use template files.
Remove support for specifying srcPaths in package.json.
Re-enable transpilation caching.
* Clean up, use file matching (similar to original) in webpack configs instead of matching function.
* Remove package lock files.
* Fix for eject.
Note: monorepos won't work after eject.
Can be fixed easily with JEST 22.0.?+ which has file pattern matches against realpaths.
* Filter tests to run only tests in monorepo components included by the app.
(Not sure this is desireable, might be cool to be able to easily run all tests in monorepo from one app.)
* Fix conditions for when to use template.
* Fix eject.
* Remove code that is not needed w/ Jest 22.
* Include all cra-comp tests in monorepo instead of trying to include only tests that are dependencies of app.
(tests can be easily filtered via jest cli if desired, e.g. 'npm test -- myapp comp1')
* Pin find-pkg version.
* Hopefully fix jest test file matching on windows by removing first slash.
* E2E tests for monorepo.
* Run monorepo tests in CI.
* Fix and test post-eject build.
* Fix e2e test.
* Fix test suite names in appveyor.
* Include individual package dirs as srcPaths instead of top-level monorepo root.
Fixes build/start after eject.
* Fix running tests after eject.
* Clean up test workspace, add some verifcations.
* Cleanup.
* Try to fix hang when running test on appveyor.
* Don't write babel or lint config to package.json when ejecting.
* Incorporate review comments.
* Simply monorepo pkg finder
* Only include monorepo pkgs if app itself is included in monorepo
* Check for specific tests in e2e
* Fixes for windows.
* Fix for kitchensink mocha tests compiling.
* Add lerna monorepo test.
* Fix lerna bootstrap on windows.
* Incorporate more review comments:
* remove support for lerna w/o yarn workspace
* add react and react-dom as devDeps to comp1 and comp2
* Add monorepo info to user guide.
* Add css modules with [name].modules.css file convention
* Add e2e for CSS Modules
* Updated based on feedback
* Change css modules class name to be deterministic and fix licences
* Update css modules class naming convention
* Update dependencies in react-scripts
* Add first pass of working dependencies for babel-preset-react-app and react-scripts
* Bump more dependency versions
* Adjust more versions and edit fix options
* Restore functionality of old preset
* Disable Uglify in iframe webpack
* Apply prettier
* Re-enable cache in dev and clean deps
* Lock packages and move babel/core to dep in preset
* Bump babel-jest
* Re-enable uglify
* Nest forceAllTransforms correctly in webpack config
* Install babel-core bridge for jest
* Add jest-cli and babel-core bridge to make tests in react-error-overlay pass
* Re-enable transform-dynamic-import
* Add dynamic import syntax support back
* Use new babel in kitchensink
* Transform modules in test
* Revert "Transform modules in test"
This reverts commit 539e46a1d77259898b7e70d778a5e43fc25edc2a.
* Attempt fix for ejected tests
* try this
* Add regenerator back
* Bump babel deps to beta.34
* Remove bad files
* Use default when requiring babel transform plugin
* Bump deps
* Try the fix?
* Oopsie
* Remove some weird things
* Run Babel on react-error-overlay tests
* Try fixing kitchensink
* Use new API for codeFrame
* Add missing (?) babelrc
* Maybe this helps?
* Maybe fix mocha
* I shouldn't have deleted this 🤦
According to this parameter's comment, it's unused but webpack-dev-server crashes without it. However, webpack-dev-server is running fine for me without this parameter.
* Convert react-error-overlay to React
* Update compile-time error overlay to use react-error-overlay components
* Refactor react-error-overlay components to container and presentational components.
* Make the compile-time error overlay a part of react-error-overlay package.
* Use react-error-overlay as dependency in react-dev-utils to show compile-time errors.
* Run Prettier
* Move the function name fix into StackFrame itself
* Fix clicking on source code snippet to open the code in editor
* Use exact objects + minor style tweak
* Don't linkify frames that don't exist on the disk
* Fix lint
* Consolidate iframe rendering logic
* Remove circular dependency between react-dev-utils and react-error-overlay
* Fix lint
* Fix decoupling of react-dev-utils and react-error-overlay by moving middleware
* Deduplicate identical errors
* Allow importing package.json
* Remove package.json import from App.js template
* fix importing package.json
* Rename variable to reflect path is relative to root
* Check for both package & package.json in ModuleScopePlugin
* Use regex to check relative path to package.json
* Strictly enforce package.json extension on scope plugin
* Add allowedPaths to ModuleScopePlugin ctor and use it to allow app package.json
* Remove package.json import from App.js template
* Add package.json to react-scripts/template, show package version and name in the template
* Remove import package.json from template
* Remove template/package.json and its references in code
* Update ModuleScopePlugin.js
* Update README.md
* Use oneOf to resolve correct loader
* Add html and json fallthrough again
* Use oneOf to resolve correct loader in dev
* Document file-loaders `js` exclusion
* Remove `jsx` from exclusion in prod config
* Adding postcss-flexbugs-fixes
Using postcss-flexbugs-fixes to fix all flexbug's issues.
* Adding flexbox: 'no-2009' to Autoprefixer
It will add flexbox prefixes only for final and IE versions of
specification.
* Support hoisting react-scripts
* require.resolve() loaders and configs
This makes it so that loaders and configs are resolved relative to the config rather than to the app. This seems to make more sense to me.
* Browser sort is not stable
* Fix ordering of final message
* Register the warning capture
* Display only createElement warnings
* Use different method name
* Fix regression
* Ignore errors with only node_module files
* Ignore null files, too
* Revise count
* Revise warning
* Update overlay.js
* Add support for https://github.com/facebook/react/pull/9679
* Use absolute paths
* Trim path if it's absolute
* Make sure it's an absolute path
* Oops
* Tweak for new behavior
* Make it safer
* More resilient warnings
* Prettier output
* Fix flow
* ༼ つ ◕_◕ ༽つ stack-frame-overlay
* Fix linting
* Remove auto overlay
* Fix e2e
* Pull in the rest
* Appease flow
* Correct dep
* Remove old repo references
* Check flow on test
* Test overlay in e2e
* Add cross env
* Rename package
* Make sure it gets built post-install
* Update the README
* Remove extra builds now that there's a postinstall script
* Revert "Remove extra builds now that there's a postinstall script"
This reverts commit 8bf601dbd36c1e0da7f785fa9ade70ab08ed8772.
* Remove broken script
* Fix some dev ergo
