You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: ELOOP: too many symbolic links encountered, scandir <a very long path here (due to recursion)>
Please give us a sample of your gulpfile
see above
Terminal output / screenshots
[14:24:12] Error: ELOOP: too many symbolic links encountered, scandir '/usr/src/app/.Build/web/typo3conf/ext/comot/.Build/web/typo3conf/ext/comot/.Build/web/typo3conf/ext/comot/.Build/web/typo3conf/ext/comot/.Build/web/typo3conf/ext/comot/.Build/web/typo3conf/ext/comot/.Build/web/typo3conf/ext/comot/.Build/web/typo3conf/ext/comot/...
Please provide the following information:
OS & version: WSL2
node version (run node -v): 20.11.1
npm version (run npm -v): 10.2.4
gulp version (run gulp -v): 5
Additional information
The project's .Build folder contains the path .Build/web/typo3conf/ext/comot/ which itself is symlink back to the project's root.
(This is created by the testing framework of TYPO3 and necessary to execute the PHP unit tests.)
I don't understand why the .Build path is even considered/touched. My src requires only a single specific file.
The text was updated successfully, but these errors were encountered:
I gave gulp 5 a shot and ran into a problem.
What were you expecting to happen?
Run a simple copy job as it did with gulp 4.
What actually happened?
Please give us a sample of your gulpfile
see above
Terminal output / screenshots
Please provide the following information:
node -v
): 20.11.1npm -v
): 10.2.4gulp -v
): 5Additional information
The project's
.Build
folder contains the path.Build/web/typo3conf/ext/comot/
which itself is symlink back to the project's root.(This is created by the testing framework of TYPO3 and necessary to execute the PHP unit tests.)
I don't understand why the .Build path is even considered/touched. My
src
requires only a single specific file.The text was updated successfully, but these errors were encountered: