-
Notifications
You must be signed in to change notification settings - Fork 2
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
Error due to node_modules and too many sub-directories #3
Comments
Thanks @jlahijani for the report. I have made a quick fix which I hope should work - please let me know how it goes. You will find a module config setting: Paths of parent directories to exclude from migration Enter:
in that and I think it should solve the problem. |
Using PW 3.0.12. Seems to be an issue when exporting. I made sure to put node_modules in the ignore list. Here's the error I'm getting.
(note: on Windows with WAMP) |
@jlahijani - is this fixed by the try/catch in your PR? If so, then this should be fixed in the latest version. Please close if you think appropriate. |
I have a Gulp-based frontend workflow, and as a result, a "node_modules" folder appears in my /site/templates/ folder, which is normal.
Some Node modules have many many nested subdirectories, which sometimes hits a limitation on Windows. When trying to Export using ProcessMigrator, I get an error which suggests that may be the issue:
Perhaps completely ignoring "node_modules" would be a good idea, or at least a configuration option to. This could also apply to "bower_components" when using bower.
The text was updated successfully, but these errors were encountered: