61–70 of 76 posts
Earlier quoted context omitted.
If you want to learn from source code, source available is all you need.
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.
* https://github.com/excalidraw/excalidraw * 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
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 want to ask the same question for Python and Go. I'd love to see some quality OSS using Python or Go and contribute to them if I can.
I recommend to look at such project on go https://github.com/containerd/containerd https://github.com/tailscale/tailscale
Maybe at some point it is nice to look at them, but they don't look very approachable to me, if I just want to take a look at how code is normally written in go beyond some AoC-exercises. Like useful common patterns and such.
I'm part of the team that maintains a digital wallet browser extension with a really clean codebase — check it out. https://github.com/tallyhowallet/extension
This is not exactly a codebase, but I believe it merits mention in this thread as a great TypeScript learning resource. https://type-level-typescript.com/ A short online course about intermediate-to-advanced level TypeScript.
The course is paid but the exercises are free on GitHub, you just won't get any explanations if you get an exercise wrong.
* https://github.com/excalidraw/excalidraw * 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
https://github.com/excalidraw/excalidraw/blob/master/src/com... files like this make me feel like my files aren’t too long after all :)
Earlier quoted context omitted.
Is server source code included? If yes, in which package is it? Thanks!
Most of the code is here: https://github.com/Linen-dev/linen.dev/tree/main/apps/web We're in the process of moving components out in to their own package so they can be shared between different clients. https://github.com/Linen-dev/linen.dev/tree/main/packages We use next js but is in the process of migrating the backend code to a node service
Would you mind sharing why? I'm curious because I'm building a Next.js-powered Slack app currently.
* https://github.com/excalidraw/excalidraw * 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
I've decided to dive deep into cal.com. Its tech stacks are exactly same as mine.
And thank everyone giving advice!
You should contribute to open source project that has reviewers, it's like doing a test and having it graded by teachers.
I will pick one interesting open source project and start contributing.