ts-routes VS mattermost-webapp

Depends whether you actually want to learn TypeScript or just how to consume it. More than 90% of TypeScript code I've seen is not actually taking advantage of TypeScript's static analysis capabilities to write safer more scalable code and is instead just being used as glorified autocomplete.

If you actually want to leave, then take a look at the implementation for stuff like Zod: https://github.com/colinhacks/zod/tree/master/src/helpers

You can do some really powerful stuff that hugely benefits your team. A decent example I stumbled across recently when I went to release my own library (that does the same thing) is https://github.com/leancodepl/ts-routes

I don't know about the quality, but Mattermost is in TS: https://github.com/mattermost/mattermost-webapp

On the web platform end, we merged the upgrade to React 17 (again) into master, and performed a bunch of (more minor) dependency updates while at it. We also continue our journey towards using MUI-based menus.

On the web platform end, we continue the work on menu components, found and fixed the issue that marked a whole lot of channels as unread last week (with GarphQL enabled). We’ve also been working on performance regression tests. And we’re upgrading moar dependencies.

On the web platform end, the team has been working on unifying post components (and cleaning up afterwards), more fighting with Webpack and friends in the context of the front-end part of the multi-product architecture, testing out a prototype of menus based on Material UI, and the regular cycle of dependency updates.

mattermost : https://github.com/mattermost/mattermost-webapp

On the web platform end, beside being overwhelmed by anticipation of the upcoming new joiners, we’re making good progress in getting webpack federation ready to be merged. This will be a solid step towards the multi-product architecture on the front-end. The upgrade to React 17 is also almost there. Beyond that, as mentioned, we’re fixing a few issues in GraphQL before we enable it again on community.

On the web platform end, we are experimenting with “theme weeks” as a budgeting hack to work on important but not urgent stuff. This first theme week (and this will likely be a recurring one) is focused on 🥁 performance! We’re pulling in a whole bunch of tickets accumulated over time of smaller things we can optimize for performance. Some of these improvements are already landing.

Platform involves work in many of our “highest traffic” repositories. I’m still figuring out reasonable ways how to keep up with what’s happening in the webapp, server, mobile repos as well as everything related to QA.

Most projects on GitHub have CONTRIBUTING.md file which describes how you can contribute, so you can start from there. Generally I'd say getting to meaningful contributions is very difficult for someone without real-world development experience, so if you choose to do this it won't be easy. On the other hand, this is precisely why employers prefer people who already have this experience -- it takes time and effort and not everyone makes it even with support from senior collegues.

Mattermost was the closest I was able to find and until their cloud beta finishes you have to setup a server to run them. With a Github or Google identity you are one click away from running Uclusion (and with any email several clicks) - no credit card required.