4 ms·
* https://github.com/excalidraw/excalidraw https://github.com/excalidraw/excalidraw * https://github.com/calcom/cal.com https://github.com/calcom/cal.com * ht
by FBISurveillance 4y ago
* https://github.com/excalidraw/excalidraw https://github.com/excalidraw/excalidraw
* https://github.com/calcom/cal.com https://github.com/calcom/cal.com
* https://github.com/supabase/supabase https://github.com/supabase/supabase
* https://github.com/appwrite/appwrite https://github.com/appwrite/appwrite
* https://github.com/n8n-io/n8n https://github.com/n8n-io/n8n
* https://github.com/appsmithorg/appsmith https://github.com/appsmithorg/appsmith
* https://github.com/directus/directus https://github.com/directus/directus
* https://github.com/Budibase/budibase https://github.com/Budibase/budibase
- robertwt7 4y agohttps://github.com/hasura/graphql-engine https://github.com/hasura/graphql-engine https://github.com/hoppscotch/hoppscotch https://github.com/hoppscotch/hoppscotch https://github.com/nestjs/nest https://github.com/nestjs/nest
- arcturus17 4y agoThanks, these are extremely interesting beyond TypeScript.
- TAForObvReasons 4y agon8n 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"
- johnfn 4y agoIf you want to learn from source code, source available is all you need.
- NetOpWibby 4y agoYou know people gotta be pedantic on here.
- TAForObvReasons 4y agoThere 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.
- motoxpro 4y agoThe ones linked aren’t leaks. So nothing to worry about there.
- thisjeremiah 4y agohttps://github.com/excalidraw/excalidraw/blob/master/src/components/App.tsx https://github.com/excalidraw/excalidraw/blob/master/src/com... files like this make me feel like my files aren’t too long after all :)
- MuffinFlavored 4y agofor anybody who doesn't want to click, it's 6400+ lines of code
- bradwood 4y agowell, linting rules for imports probably added 30%
- vijaybritto 4y agoExtremely 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!
- Peer_Rich 4y agohey there, cofounder of cal.com here. thank you for the flowers -- means a lot. zomars (https://github.com/zomars https://github.com/zomars) has been making a ton of great improvements lately
- pototo666 4y agoThanks for the list. I've decided to dive deep into cal.com. Its tech stacks are exactly same as mine. And thank everyone giving advice!
- Peer_Rich 4y agocofounder of cal.com here, thank you @pototo666 the typescript, tailwind, nextjs, trpc stack has been amazing so far
- FBISurveillance 4y agoHey 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.
- mohanarpit 4y agoCo-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. :)