add next 12.x support to @cypress/react
See original GitHub issueWhat would you like?
We would like @cypress/react
to support nextjs
12.x
Why is this needed?
We’d like to be able to upgrade to nextjs 12.x - in order to take advantage of the new middleware API. Sadly though, it looks like @cypress/react
is not quite ready to support nextjs 12.x atm.
Other
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:15 (5 by maintainers)
Top Results From Across the Web
React Component Testing - Cypress Documentation
Cypress Component Testing currently supports React 16+ with the following frameworks: Create React App; Next.js; React with Vite; React with Webpack. Tutorial.
Read more >Testing React Apps In 2022 With Cypress: An In-Depth Guide ...
I prepared a project that you can use to follow along. It's a Next.js app that needs some testing love. We'll write a...
Read more >Testing | Next.js
Learn how to set up Next.js with three commonly used testing tools — Cypress, Playwright, Jest, and React Testing Library.
Read more >Use Cypress with Next.js and Nx to battle test your React ...
Nx also automatically generates Cypress e2e tests for the various Storybook ... automated setup of Next.js apps with TypeScript support ...
Read more >The Complete Guide to Testing React Native App Using Cypress
Let's put our Expo local URL into cypress.json file so our tests know what to load by default. cypress.json. 1
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like the API for getNextJsBaseWebpackConfig has changed from v12.1.5 to v12.1.6 which is the API we rely on to grab the Next webpack config. Quick test changing
isServer: false
tocompilerType: 'client'
here seems to fix the issue. Will pick this up at the beginning of next week, hopefully is as straightforward as it seems and if so we’ll have this fixed soon.Absolutely.
Thank you very very much @lmiller1990 for taking care. Same to @leerob for jumping in.