-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Can't ran any of the codemods #1105
Comments
Also just upgraded. Same issue. |
Same issue here Update: I went back and tried the upgrade again and had some success. This was an add-on upgrade from 3.12 -> 3.16. I'm not sure my steps fixed the issue but I wanted to document them
These codemods failed with the error: I'll work on this some more and update again 3/10/21 Update to the update From my last update, I didn't realize that I upgraded all the way to 3.25, not 3.16. When I reversed the update and then updated to 3.16 I could run the codemods without errors. I still needed to be on Node 12. |
I'm seeing this same issue, I believe, when using node 12.x. When I revert to node 10.x it appears to be resolved. |
@ballPointPenguin are you using yarn or npm? I’m using yarn and was seeing errors related to node-gyp errors related to node 14. Rolling back to 12 fixed those errors and I could use ember-cli-update. I’m planning to test against npm |
@maxwondercorn I'm using npm 6. |
Same issue, any updates on this issue? |
Wondering if anyone has a fix for this? I have a smaller app I would like to update but cannot run codemods on it because of this issue. |
Look at this commit for node 12 and 14 versions which work 355af98 The file in question mentions version greater than 14.5 have a regression and will not work. Lines 3 to 6 in 07ca9a2
This should be mentioned in the README or somewhere like that.... |
Updating app to the latest Ember version (3.24.0) succeeded but running any of the codemods after that always fail:
Output from command with debug flag:
After quick research it looks like it might be an issue with isaacs/node-graceful-fs#192 but I'm not sure how to fix it.
The text was updated successfully, but these errors were encountered: