if you create a symlink pointing to .. it silently freezes the packager up to out of memory

ln -s .. foo

react-native bundle --entry-file index.ios.js --bundle-output out
# aka a Release build

will infinitely freeze the packager without any error or any log. After like 40minutes, it ends with a out of memory. not very helpful DX 😦

[10:27:33 PM] <START> Building Dependency Graph
[10:27:33 PM] <START> Crawling File System
[10:27:34 PM] <START> find dependencies

^ Stopped here

We had hard time figuring out the problem (and obviously we accidentally created that symlink) so YEAH it’s not very critical. but it’s a terrible experience when you fall into it and packager don’t want to build JUST in Release mode… so it would be great to fix it in some way, here is thoughts:

• packager to ignore symlinks (if it doesn’t support it, drop it)
• prevent file exploration loop (going back again back in one of the explored folder should be forbidden)
• log a more useful warning when you traverse symlink… (at least in DEBUG mode? even enabling the export DEBUG= thing didn’t even helped!)

[Kureev]

I’ll try to take a deeper look into it when I have a time

[facebook-github-bot]

@charpeni tells me to close this issue. If you think it should still be opened let us know why.