-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Cypress Component Testing: "Module parse failed: parser.destructuringAssignmentPropertiesFor is not a function" #16803
Comments
This stackoverflow post suggested that the following could cause the error:
Looking at my repo:
Upgrading webpack to latest (^5.85.0) in |
@Nick-Lucas thanks for opening the issue. do you have a repo I can take a look at? |
Afraid I haven't had a chance to try and reproduce dry, and now we're getting a new King in Blighty so won't be able to share deeper details until Tuesday. As above I've resolved the issue by upgrading the package.json webpack version. Nx is using a newer version internally than it upgraded me to during the migration path - this repo started out on Nx 13 or 14 and has been migrated regularly up until today - so I believe the next Nx version just needs a migration added to check that webpack is in-line with @nx/webpack's version. Cypress version is also what Nx prescribed I believe. Full repro conditions as I understand them:
|
I just had the same issue when going from 16.0.3 to 16.1.3 on my React application. I hope to dig in over the next day or so to isolate the issue, my upgrade only contained package version bumps. |
I just had to change my |
as @madelk stated, I changed the same thing and was able to get past the issue. Mismatching webpack versions caused the issue. |
Hi all, sorry for getting back late on this. but confirmed that the mixed match webpack versions are the issue. I'll add a migration the @nx/webpack to bump that version in peoples package.json if it exists which should solve the issue for anyone down the road. also if you're not using webpack outside of @nx/webpack. i.e. not calling webpack directly anywhere. it should be safe to remove the dep from your package.json since it's a dep of @nx/webpack. |
@barbados-clemens Thanks Caleb, that will definitely help! |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
After upgrading from 15.x to 16.1.0 component testing does not run
Expected Behavior
Component testing works as before
GitHub Repo
No response
Steps to Reproduce
Upgrade an existing project with component testing, and according to the error have a file like this:
./src/environments/index.ts
:Nx Report
Failure Logs
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: