files like this make me feel like my files aren’t too long after all :)
Monorepo tooling, Build optimizations, complex webpack setups, performance tuning. For example from the above list I went through cal.com repo and I saw that the way they have organized dev and prod builds and openAPI spec browsing tooling is very good. This is exemplary for anyone wanting to look at good ways to setup a project!
I've decided to dive deep into cal.com. Its tech stacks are exactly same as mine.
And thank everyone giving advice!
We love Typescript and chose it to take advantage of static type checking. At Apspmith, since we are a small team, we wanted to reduce management overheads and opted for a monorepo layout. Typescript went a long way in helping us organize the code into modules and let our build scripts compile relevant modules for each changeset.
Having said that, Appsmith has been a learning experience in efficiently running a large project with lots of files. Feel free to dig into our source code to learn from our experiences. :)
* https://github.com/calcom/cal.com
* https://github.com/supabase/supabase
* https://github.com/appwrite/appwrite
* https://github.com/n8n-io/n8n
* https://github.com/appsmithorg/appsmith
* https://github.com/directus/directus
* https://github.com/Budibase/budibase