Skip to content
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

Response code 404 (Not Found) when Vite app is successfully running. #293

Closed
bluebill1049 opened this issue Feb 8, 2021 · 3 comments · Fixed by #294
Closed

Response code 404 (Not Found) when Vite app is successfully running. #293

bluebill1049 opened this issue Feb 8, 2021 · 3 comments · Fixed by #294

Comments

@bluebill1049
Copy link

bluebill1049 commented Feb 8, 2021

Hi,

I am trying to migrate from CRA to Vite

However, I am encountering an issue with running the app within the cypress GitHub action.

here is a screenshot of the issue

Screen Shot 2021-02-08 at 7 48 53 pm

PR: react-hook-form/react-hook-form#4132

More Context:

  • nothing else is changed at the config level, except switch from CRA to Vite.
  • running it locally is fine.

Screen Shot 2021-02-08 at 8 01 00 pm

  • standard action script
name: E2E Test

on: [pull_request]

jobs:
  cypress-run:
    runs-on: ubuntu-16.04
    steps:
      - uses: actions/checkout@v2
      - name: Cypress run
        uses: cypress-io/github-action@v2
        env:
          DEBUG: 'cypress:*'
        with:
          start: npm run start:app
          wait-on: 'http://localhost:3000/'
          wait-on-timeout: 60
@bahmutov bahmutov changed the title Response code 404 (Not Found) when app is successfully running. Response code 404 (Not Found) when Vite app is successfully running. Feb 8, 2021
@bahmutov
Copy link
Contributor

bahmutov commented Feb 8, 2021

I think this is the same issue as bahmutov/start-server-and-test#294 which just needs Accept header update. I will take a look, thanks for providing a link to the reproducible example

@github-actions
Copy link

github-actions bot commented Feb 8, 2021

🎉 This issue has been resolved in version 2.8.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@bluebill1049
Copy link
Author

Amazing! thanks very much for the fix @bahmutov ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants