diff --git a/.eslintrc.json b/.eslintrc.json index b642bbc5c14..40029410cce 100644 --- a/.eslintrc.json +++ b/.eslintrc.json @@ -4,7 +4,8 @@ "browser": true, "commonjs": true, "node": true, - "es6": true + "es6": true, + "jest": true }, "parserOptions": { "ecmaVersion": 2018 diff --git a/.github/workflows/integration.yml b/.github/workflows/integration.yml new file mode 100644 index 00000000000..1249f20532f --- /dev/null +++ b/.github/workflows/integration.yml @@ -0,0 +1,36 @@ +name: Integration Tests + +on: + push: + branches: + - master + pull_request: + branches: + - master + +jobs: + job: + runs-on: ${{ matrix.os }} + strategy: + matrix: + os: ['ubuntu-latest', 'macos-latest', 'windows-latest'] + node: ['10', '12', '14'] + steps: + - uses: actions/checkout@v2 + - name: Setup node + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node }} + - name: Cache dependencies + id: cache + uses: actions/cache@v2 + with: + path: | + node_modules + */*/node_modules + key: ${{ runner.os }}-${{ hashFiles('**/yarn.lock', './yarn.lock') }} + - name: Install packages + if: steps.cache.outputs.cache-hit != 'true' + run: yarn --frozen-lockfile --prefer-offline + - name: Run integration tests + run: yarn test:integration diff --git a/azure-pipelines-test-job.yml b/azure-pipelines-test-job.yml index 116d2f87e23..cd6cc7c67c9 100644 --- a/azure-pipelines-test-job.yml +++ b/azure-pipelines-test-job.yml @@ -6,8 +6,8 @@ parameters: name: '' testScript: '' configurations: - LinuxNode10: { vmImage: 'ubuntu-16.04', nodeVersion: 10.x } LinuxNode12: { vmImage: 'ubuntu-16.04', nodeVersion: 12.x } + LinuxNode14: { vmImage: 'ubuntu-16.04', nodeVersion: 14.x } jobs: - job: ${{ parameters.name }} diff --git a/azure-pipelines.yml b/azure-pipelines.yml index 3c89363208b..32c7a5c166d 100644 --- a/azure-pipelines.yml +++ b/azure-pipelines.yml @@ -26,10 +26,10 @@ jobs: # ****************************************************************************** # Installs test suite # ****************************************************************************** - - template: azure-pipelines-test-job.yml - parameters: - name: Installs - testScript: tasks/e2e-installs.sh + # - template: azure-pipelines-test-job.yml + # parameters: + # name: Installs + # testScript: tasks/e2e-installs.sh # ****************************************************************************** # Kitchensink test suite @@ -42,25 +42,25 @@ jobs: # ****************************************************************************** # Kitchensink Eject test suite # ****************************************************************************** - - template: azure-pipelines-test-job.yml - parameters: - name: KitchensinkEject - testScript: tasks/e2e-kitchensink-eject.sh + # - template: azure-pipelines-test-job.yml + # parameters: + # name: KitchensinkEject + # testScript: tasks/e2e-kitchensink-eject.sh # ****************************************************************************** # Behavior test suite # ****************************************************************************** - - template: azure-pipelines-test-job.yml - parameters: - name: Behavior - testScript: tasks/e2e-behavior.sh - configurations: - LinuxNode10: { vmImage: 'ubuntu-16.04', nodeVersion: 10.x } - LinuxNode12: { vmImage: 'ubuntu-16.04', nodeVersion: 12.x } - WindowsNode10: { vmImage: 'windows-2019', nodeVersion: 10.x } - WindowsNode12: { vmImage: 'windows-2019', nodeVersion: 12.x } - MacNode10: { vmImage: 'macOS-10.15', nodeVersion: 10.x } - MacNode12: { vmImage: 'macOS-10.15', nodeVersion: 12.x } + # - template: azure-pipelines-test-job.yml + # parameters: + # name: Behavior + # testScript: tasks/e2e-behavior.sh + # configurations: + # LinuxNode12: { vmImage: 'ubuntu-16.04', nodeVersion: 12.x } + # LinuxNode14: { vmImage: 'ubuntu-16.04', nodeVersion: 14.x } + # WindowsNode12: { vmImage: 'windows-2019', nodeVersion: 12.x } + # WindowsNode14: { vmImage: 'windows-2019', nodeVersion: 14.x } + # MacNode12: { vmImage: 'macOS-10.15', nodeVersion: 12.x } + # MacNode14: { vmImage: 'macOS-10.15', nodeVersion: 14.x } # ****************************************************************************** # Old Node test suite diff --git a/docusaurus/docs/advanced-configuration.md b/docusaurus/docs/advanced-configuration.md index 7cc9f14f888..34144ce6040 100644 --- a/docusaurus/docs/advanced-configuration.md +++ b/docusaurus/docs/advanced-configuration.md @@ -15,7 +15,7 @@ You can adjust various development and production settings by setting environmen | PORT | βœ… Used | 🚫 Ignored | By default, the development web server will attempt to listen on port 3000 or prompt you to attempt the next available port. You may use this variable to specify a different port. | | HTTPS | βœ… Used | 🚫 Ignored | When set to `true`, Create React App will run the development server in `https` mode. | | WDS_SOCKET_HOST | βœ… Used | 🚫 Ignored | When set, Create React App will run the development server with a custom websocket hostname for hot module reloading. Normally, `webpack-dev-server` defaults to `window.location.hostname` for the SockJS hostname. You may use this variable to start local development on more than one Create React App project at a time. See [webpack-dev-server documentation](https://webpack.js.org/configuration/dev-server/#devserversockhost) for more details. | -| WDS_SOCKET_PATH | βœ… Used | 🚫 Ignored | When set, Create React App will run the development server with a custom websocket path for hot module reloading. Normally, `webpack-dev-server` defaults to `/sockjs-node` for the SockJS pathname. You may use this variable to start local development on more than one Create React App project at a time. See [webpack-dev-server documentation](https://webpack.js.org/configuration/dev-server/#devserversockpath) for more details. | +| WDS_SOCKET_PATH | βœ… Used | 🚫 Ignored | When set, Create React App will run the development server with a custom websocket path for hot module reloading. Normally, `webpack-dev-server` defaults to `/ws` for the SockJS pathname. You may use this variable to start local development on more than one Create React App project at a time. See [webpack-dev-server documentation](https://webpack.js.org/configuration/dev-server/#devserversockpath) for more details. | | WDS_SOCKET_PORT | βœ… Used | 🚫 Ignored | When set, Create React App will run the development server with a custom websocket port for hot module reloading. Normally, `webpack-dev-server` defaults to `window.location.port` for the SockJS port. You may use this variable to start local development on more than one Create React App project at a time. See [webpack-dev-server documentation](https://webpack.js.org/configuration/dev-server/#devserversockport) for more details. | | PUBLIC_URL | βœ… Used | βœ… Used | Create React App assumes your application is hosted at the serving web server's root or a subpath as specified in [`package.json` (`homepage`)](deployment#building-for-relative-paths). Normally, Create React App ignores the hostname. You may use this variable to force assets to be referenced verbatim to the url you provide (hostname included). This may be particularly useful when using a CDN to host your application. | | BUILD_PATH | 🚫 Ignored | βœ… Used | By default, Create React App will output compiled assets to a `/build` directory adjacent to your `/src`. You may use this variable to specify a new path for Create React App to output assets. BUILD_PATH should be specified as a path relative to the root of your project. | diff --git a/docusaurus/docs/using-the-public-folder.md b/docusaurus/docs/using-the-public-folder.md index 71266db6f81..a33c3a29ec8 100644 --- a/docusaurus/docs/using-the-public-folder.md +++ b/docusaurus/docs/using-the-public-folder.md @@ -60,7 +60,7 @@ The `public` folder is useful as a workaround for a number of less common cases: - You need a file with a specific name in the build output, such as [`manifest.webmanifest`](https://developer.mozilla.org/en-US/docs/Web/Manifest). - You have thousands of images and need to dynamically reference their paths. -- You want to include a small script like [`pace.js`](https://github.hubspot.com/pace/docs/welcome/) outside of the bundled code. +- You want to include a small script like [`pace.js`](https://github.com/CodeByZach/pace) outside of the bundled code. - Some libraries may be incompatible with webpack and you have no other option but to include it as a `