chore(deps-dev): bump typescript-eslint from 8.14.0 to 8.15.0 #18817
Workflow file for this run
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: Developing with Yari | |
| on: | |
| pull_request: | |
| jobs: | |
| build: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: actions/checkout@v4 | |
| - uses: actions/checkout@v4 | |
| with: | |
| repository: mdn/content | |
| path: mdn/content | |
| - name: Setup Node.js environment | |
| uses: actions/setup-node@v4 | |
| with: | |
| node-version-file: ".nvmrc" | |
| cache: yarn | |
| - name: Cache @vscode/ripgrep bin | |
| uses: actions/cache@v4 | |
| with: | |
| key: vscode-ripgrep-bin-${{ runner.os }}-${{ runner.arch }}-${{ hashFiles('yarn.lock') }} | |
| path: node_modules/@vscode/ripgrep/bin/ | |
| - name: Install all yarn packages | |
| run: yarn --frozen-lockfile | |
| env: | |
| # https://github.com/microsoft/vscode-ripgrep#github-api-limit-note | |
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | |
| - name: Setup kernel for react native, increase watchers | |
| run: | | |
| # When running Yari on Linux, you might get the | |
| # "Error: ENOSPC: System limit for number of file watchers reached" error. | |
| # This, resolves that. | |
| # Source https://github.com/expo/expo-github-action/issues/20#issuecomment-541676895 | |
| echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p | |
| - name: Start the dev server | |
| env: | |
| REACT_APP_WRITER_MODE: true | |
| # Remember, the mdn/content repo got cloned into `pwd` into a | |
| # sub-folder called "mdn/content" | |
| CONTENT_ROOT: "${{ github.workspace }}/mdn/content/files" | |
| run: | | |
| # Sanity check that the mdn/kitchensink page is there. If you don't do | |
| # this, and the file has accidentally or intentionally been deleted, | |
| # unfortunately the error messaging can be very misleading because the | |
| # tests would assume there's something wrong with the code instead of | |
| # the content if loading this page fails. | |
| ls "$CONTENT_ROOT/en-us/mdn/kitchensink" | |
| yarn build:prepare | |
| yarn start > /tmp/stdout.log 2> /tmp/stderr.log & | |
| - name: Wait for servers | |
| run: | | |
| # Just a slight delay to wait until the dev server is ready. | |
| sleep 3 | |
| curl --retry-connrefused --retry 5 http://localhost:5042 > /dev/null | |
| curl --retry-connrefused --retry 5 --silent http://localhost:3000 > /dev/null | |
| - name: Test viewing the dev server | |
| run: | | |
| yarn test:developing | |
| - name: Debug server's stdout and stderr if tests failed | |
| if: failure() | |
| run: | | |
| echo "STDOUT..................................................." | |
| cat /tmp/stdout.log | |
| echo "" | |
| echo "STDERR..................................................." | |
| cat /tmp/stderr.log |