opensource.microsoft.com VS rushstack

If you want to contribute to big projects like Microsoft or Drupal on your portfolio, feel free. However, if you want to increase your chances of getting your contributions reviewed and merged, I highly recommend aiming for smaller projects. Smaller open source projects tend not to get as crowded as others, which means you might get a higher chance of your contribution being reviewed and merged at a quick pace. As a contributor, I wanted to use Hacktoberfest as an opportunity to work with YAML files for open source projects. Luckily for me, I have been talking to Arshad Khan about this on X(Twitter), so I created greetings YAML files for their projects, FarmHub, Curls, and Tindog. It was a bit of a learning curve as the greetings won’t go through, but after reading that permissions: write-all is helpful in making third-party greetings work, I added that to the files, and bam, my PRs got merged! Hold on, before, you rush off to make Pull Requests, there’s just one strategy that I want to share with you.

Jesse what the fuck are you on about? Open source is pretty neat but you know microsoft has a open source page. If you are gonna say but linux blah blah blah microsoft is a platinum linux foundation member

M$ also has a page with some of their projects and contributions. https://opensource.microsoft.com/

Microsoft has come a really long way in expanding their platform out. They open sourced PowerShell and .NET are actively promoting others ( https://opensource.microsoft.com ) and have full Linux cloud support on Azure.

Microsoft themselves is one of the biggest open source contributors in the world. They've moved big projects like PowerShell to be completely open source. They even own GitHub and are one of the top Linux contributors. https://opensource.microsoft.com

It's ok, the commit is enough

If you're looking to recreate the ease of a monorepo with eslint/prettier, I've used the rushstack eslint patch to ship an eslint package which is almost fully self-contained, not just config, but dependencies as well: https://github.com/microsoft/rushstack/tree/main/eslint/eslint-patch

I highly recommend rushstack. It’s a suite of tools for managing TypeScript monorepos. I use it at work and never want to go back to working without it.

https://rushjs.io/ and https://rushstack.io/

Rush Stack. It’s an opinionated, batteries-included toolset for working with large monorepos. It’s highly extensible and pluggable, and has built-in support for a lot of common tasks. My team uses it at work to support a couple dozen projects and at this point I can’t imagine managing a monorepo without it. It has significant adoption within and support from Microsoft, and monthly public dev meetings with contributors from a number of other companies, so I really don’t think it’s going to disappear any time soon. From what I’ve seen, it’s a very healthy project that’s continuing to grow in support and adoption.

Tools like Lerna, Bazel, Nx, Rush, Turborepo, to name a few. Lerna is probably the grand daddy of all monorepo tools. CRA, Babel, Jest are a few projects that use it. Bazel has been refined and tested for years at Google to build heavy-duty, mission-critical infrastructure, services, and applications. Turborepo is the monorepo for Vercel, the leading platform for frontend frameworks. These tools can help keep your monorepo workspaces fast, understandable and manageable.

We don’t use backend node, I work in a big typescript monorepo and use Typescript to build plugins for compiling, packing, and testing, leveraging Rush and Heft on the client side (https://github.com/microsoft/rushstack) run via node

I guess I'm not alone wishing that rush uses commit messages for change log generation. It's actually not so difficult (once it's done 😎).

See: ONNX/ONNX Runtime, VSCode, Rush, & countless others

To late to edit or delete my comment above but just to set it straight I just learned that the whole lerna debacle linked above was a nothing-burger aka “fake news”.

https://github.com/microsoft/rushstack/issues/673#issuecomme...