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

feat(next): support nextjs cypress component testing #16292

Merged

Conversation

barbados-clemens
Copy link
Contributor

@barbados-clemens barbados-clemens commented Apr 13, 2023

Current Behavior

No preset for running CT with NextJS

Expected Behavior

Nx + NextJS CT support

Related Issue(s)

Fixes #14363

@vercel
Copy link

vercel bot commented Apr 13, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nx-dev ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 21, 2023 3:41pm

wip

wip

wip

wip

wipp

wip

working
@barbados-clemens barbados-clemens enabled auto-merge (squash) April 21, 2023 16:35
@barbados-clemens barbados-clemens self-assigned this Apr 21, 2023
@barbados-clemens barbados-clemens added the scope: testing tools Issues related to Cypress / Jest / Playwright / Vitest support in Nx label Apr 21, 2023
@barbados-clemens barbados-clemens merged commit 06a885a into nrwl:master Apr 21, 2023
@barbados-clemens barbados-clemens deleted the feat/nextjs-cypress-ct branch April 21, 2023 19:51
@github-actions
Copy link

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
scope: testing tools Issues related to Cypress / Jest / Playwright / Vitest support in Nx
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support Cypress Component Testing with Next.js
4 participants