ESLint, Prettier, the TS LSP, etc. are going bananas on huge files :p GH won't even display it. Splitting eases the work on the IDE.
It's more about DX, I admit ^^.
Partly because of that the repo isnt using Prettier but dprint ;p i dont experience a lot of IDE slowdown when working with this and the repo is using eslint (and TS LSP ofc)
I forgot one thing that had bitten me in the past : Syntax highlighting, in VSCode, is more prone to break on huge, complicated files. Breaking them up can help pinpoint oddities.
Often I don't get what's triggering colours weirdness.
I think to some extent the reasons are historical - it was written using legacy TS modules/namespaces and it wouldnt be great for perf if things would incur property lookup costs all over the place. Since then the codebase has been migrated to use ES modules though
When working with this file I actually love that it’s all in one file, it’s easy to grep it and jump between locations, most of things are already available in scope. It’s nice
Comments
It's more about DX, I admit ^^.
Often I don't get what's triggering colours weirdness.