Co-founder of Appsmith here. Thanks a lot for mentioning our project.
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. :)
Extremely interesting projects here. Not just for typescript but also for
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!
hey there, cofounder of cal.com here. thank you for the flowers -- means a lot. zomars (https://github.com/zomars) has been making a ton of great improvements lately
Hey Peer, wanted to take a chance and say thanks (as a paying customer) for building cal.com, and doing it in public. It's been extremely helpful for me personally, I learned a lot by following your process, your handbook, and your codebase.
n8n is not open source and many of the projects are using a hybrid licensing model. Code on GitHub is "source available", not necessarily "open source"
There are plenty of proprietary source code leaks, and those are technically "source available" since the source is available, but that is not a recommended practice.
files like this make me feel like my files aren’t too long after all :)