In the extreme, with pure text editor, you want all details together where you effortlessly see them. Helper function means manual search and scroll.
But then vim gets heavy like an ide... Pick your poison.
It is really weaker with sublime or vim, at least from what I have seen. They often did not found right function even when it was in the same file and there was no ambiguity - leading to harder to read code with deep nesting and loooong functions (that really should have been split into named steps).
It does not do that at all when vim user did not bothered to configure right plugins or did not bothered to learn them.
I would gather that sublime text pushes you towards more focused, tight code, because their auto complete isn't context aware.
To your specific point, helper functions should be as close as possible to the function it is helping. If you have easy "go to function" functionality, some people will slack off on this.
Refusal to use helper fuctions also led to a lot of code repetition in various (especially on click) handlers. When you have bugs from people forgetting to change fourth place where pretty much same thing is done, then the code is bad.
We had deadlines and I really think that everything would be way more effective if we took advantages of ide and generated code that express intent better and is composed of smaller units. Instead everything took longer and complexity was pretty much unmanaged (since they refused to use helper fuctions they never learned how to use then effectively nor how to effectively modularize code - the codebas was fine while small and increasingly unmanageable as it grew).