Skip to content

merging upstream master #99

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 79 commits into from
Apr 25, 2019
Merged

merging upstream master #99

merged 79 commits into from
Apr 25, 2019

Conversation

joeycozza
Copy link

No description provided.

Jack Zhao and others added 30 commits February 20, 2019 11:47
* Upgrade dependencies

* Upgrade a couple missed deps

* Run Prettier over codebase
* add command to add files to staging after eject

* update console.log message

* wrap git add in a try/catch block

* return true & update log message

* add test to check if files were staged

* Fix check for staged files
* Add note about npx caching and link to #6119

It is necessary to uninstall any version that was previously installed for the typescript flag to work when using npx.

* Use proper casing for TypeScript

Co-Authored-By: TaylorBriggs <TaylorBriggs@users.noreply.github.com>
* Add browserslist support to @babel/preset-env

* Support @babel/polyfill in entry point
* Add Babel plug-in for Hooks; Add ESLint plug-in for Hooks (WIP)

* Fix transform destructuring loose config

* Add eslint-plugin-react-hooks to package.json

* Fix package.json's

* Fix eslint-plugin-react-hooks version

* Fix package.json

* Fix package.json

* Add eslint-plugin-react-hooks to script package.json

* Force array destructuring to work in loose mode only for known Hooks

* Update based on feedback from PR

* Add 'exhaustive-deps' lint rule

* Bump eslint-plugin-react-hooks to stable version

* Remove extraneous dependency from react-scripts
* Initial pass adding typescript-eslint

* Add warning to shared rule set

* Add documentation for setting up VSCode extension

* Provide tsconfig path to typescript-eslitn
* Update to jest 24

* Add notice about pnpResolver.js

* Formatting

* Fix linting

* Update to jest 24.1.0

* Update jest-pnp-resolver

* Swap create-react-app params in e2e scripts

* Add extraGlobals to supportedKeys

* Bump jest to 24.3.1

* Bump jest to 24.4.0

* Bumb jest to 24.5.0

* Update template dependencies jest to 24.5.0

* Debug failing test

* Remove jest-pnp-resolver

* Remove console.log

* Revert yarn.lock.cached
Sync the `babel-eslint` version between react-scripts and eslint-config-react-app
…ion (#6655)

* Change app component declaration from arrow function to regular function

* Change TypeScript template back to an arrow function
`url` was duplicated in `siteConfig.js`, both were the same value, so stripping one of them.
* Add AWS Amplify deployments to the CRA Docs

* Fixed typos

* added gif

* GIF link

* Update docusaurus/docs/deployment.md

* create-react-app to Create React App

* Update docusaurus/docs/deployment.md

* Removed extra verbiage.

* Removed GIF
* Remove project property from @typescript-eslint/parser options

The "project" property has a significant performance impact on linting,
and none our rules currently need it.

Fixes #6661.
bestseob93 and others added 29 commits April 8, 2019 19:57
This also updates our min version of Node that we ask for
* Update to core-js@3

* Remove references to @babel/polyfill
* InlineChunkHtmlPlugin works with empty publicPath

* Update as requested
Specifying the directory as part of the repository field in a
package.json allows third party tools to provide better support when
working with monorepos. For example, it allows them to correctly
construct a commit diff for a specific package.

This format was accepted by npm in [npm/rfcs#19](npm/rfcs#19).
* Set baseUrl from jsconfig.json/tsconfig.json

* Resolve the path for loading modules

* Add tests for jsconfig.json

* Add jsconfig.json

* Update packages/react-scripts/scripts/start.js

* Move baseUrl test to config folder

* Remove alias test

* Use chalk from react-dev-utils

* Add lost absolute file for typescript baseUrl test

* Update packages/react-scripts/config/modules.js

* Update other references of useTypeScript to hasTsConfig

* Fix casing of TypeScript

* Keep respecting NODE_PATH for now to support multiple module paths.

* Add test for NODE_PATH

* Add fallback if NODE_PATH is not set.

* Fix node path behavior tests

* Remove debugging code from behavior test suite

* Remove more debugging code

* Show NODE_PATH deprecation warning during build


Co-authored-by: Ian Sutherland <ian@iansutherland.ca>
Co-authored-by: Brody McKee <mrmckeb@users.noreply.github.com>
Co-authored-by: Jack Zhao <jzhao@fb.com>
* Upgrade Lerna to 3.13.2

* Remove independent argument to Lerna

* Update publish command
* Relax eslint version range

* Use semver package to compare versions during preflight check

* Cleanup package.json files whitespace
* fix: change CRA version in eject warning

* Update eject.js
* Add baseUrl documentation

* Update docusaurus/docs/importing-a-component.md

Co-Authored-By: ianschmitz <ianschmitz@gmail.com>

* Update docusaurus/docs/importing-a-component.md

Co-Authored-By: ianschmitz <ianschmitz@gmail.com>

* Simplify include to match default tsconfig.json
Fixes #6852.

I update the dependency version of fsevents because old versions was vulnerable (CWE-59). Vulnerability found with snyk.io report
 - babel-plugin-named-asset-import@0.3.2
 - babel-preset-react-app@8.0.0
 - confusing-browser-globals@1.0.7
 - create-react-app@3.0.0
 - eslint-config-react-app@4.0.0
 - react-app-polyfill@1.0.0
 - react-dev-utils@9.0.0
 - react-error-overlay@5.1.5
 - react-scripts@3.0.0
* remove padding 0 on body from default styles

* Update index.css
Typo : preache => precache
@joeycozza joeycozza merged commit fda5d5c into fs-webdev:master Apr 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.