We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Started to get webpack error once upgrading nextJS to 14.1.0
14.1.0
"@cypress/browserify-preprocessor": "^3.0.2", "@cypress/code-coverage": "^3.12.19", "@istanbuljs/nyc-config-typescript": "^1.0.2", "@testing-library/cypress": "^10.0.1", "@testing-library/jest-dom": "^5.16.5", "@testing-library/react": "^13.4.0", "@testing-library/user-event": "^14.4.3", "@types/jest": "^29.2.0", "@types/supertest": "^2.0.12", "babel-plugin-istanbul": "^6.1.1", "cypress": "^13.6.3", "cypress-mochawesome-reporter": "^3.8.0", "identity-obj-proxy": "^3.0.0", "jest": "^29.2.0", "jest-environment-jsdom": "^29.2.0", "msw": "^2.1.5", "next-router-mock": "^0.9.10", "nyc": "^15.1.0", "start-server-and-test": "^2.0.0", "supertest": "^6.3.3", "ts-jest": "^29.0.3", "whatwg-fetch": "^3.6.2"
Using nyc to instrument cypress tests to get coverage
nyc
cypress
coverage
If I remove bablerc it default back to swc from nextJS, application runs, however tests are missing its point - being instrumented.
bablerc
swc
Is started just recently to give these errors. Anything could be updated from your side? I see this plugin was updated a long time ago now.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Started to get webpack error once upgrading nextJS to
14.1.0
Using
nyc
to instrumentcypress
tests to getcoverage
If I remove
bablerc
it default back toswc
from nextJS, application runs, however tests are missing its point - being instrumented.Is started just recently to give these errors. Anything could be updated from your side? I see this plugin was updated a long time ago now.
The text was updated successfully, but these errors were encountered: