-
Notifications
You must be signed in to change notification settings - Fork 23
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
[FEATURE] Support for NextJS setups not using Babel. #425
Comments
Are you user this is Reassure issue? Reassure itself does not have a direct dependency or use of Babel. Most probably this is a Jest issue. |
Tbh I have since switched over to using Vitest and not had time to try setting up Reassure again. Do you have support for Vitest? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I'm attempting to set up Reassure for a NextJS 14 application (using the new app router, SWC, etc.) and running Reassure is complaining about Babel config which the project doesn't have.
Describe the solution you'd like
A way to implement reassure without the need for Babel.
Describe alternatives you've considered
N/A
Additional context
Here's a small snippet from the output (happy to share more detail if needed).
The text was updated successfully, but these errors were encountered: