Welcome to @jolly-kite-53356 @melodic-exabyte-60253 @orange-island-82579 @billions-football-8085👋 . We invite you to say a little something about yourself and your organization, and what motivated you to take a closer look at Pants. You’ll be helping us improve future open source outreach, so thanks very much!

Hi. I'm currently working at a company that works with a car manufacturer. I'm familiar with the concept of monorepo and I became familiar with pants because of my old job, but this time I'm the one implementing it. Keep up the good work 😊

Thank you, and good luck with your implementation project! Let us know if there's anything we can do or clarify to make that easier.

Hi I’m Gilles, I’m currently working for a financial consulting company that’s getting into the SaaS business and I am one of the lead engineers. We are currently switching over to Pants as out main build system for Python packages and applications as well as building Docker containers after much trouble cobbling together our own “build system” consisting of many shell scripts and wrangling the caching in our CI. After experimenting a bit with a couple of build systems (mainly Bazel), we decided to go with Pants as it best fit our needs. So far, we didn’t encounter many issues (except building PEX files on macOS for Docker containers, which will apparently be possible in Pants 2.16). We also have quite a large TypeScript codebase for which we are currently transitioning to using Turborepo, as Pants does not support JS/TS (yet).

Interesting! To add TS support, we need a partner to help us develop a design that understands the TS ecosystem, adds value to that ecosystem, and usefully meets the needs of a TS codebase. The partner would also be needed to give substantial feedback during development. If your team is ever interested in being that partner, do feel free to give me a ping. By the way @wide-midnight-78598 has been working on JS support. So look forward to getting to check that out. :⁠-⁠)

Actually, we have an early PR for some more JS support, but not from me - my stuff is currently private, with it on the Pants backburner with the other things I need to do first. Very excited about this! https://github.com/pantsbuild/pants/pull/18138 That's from @worried-painter-31382 - which adds NPM support (and then eventually defer into the appropriate build tools). Here's the associated GH discussion: https://github.com/pantsbuild/pants/discussions/17357

Ah thank you for that correction. Sorry for the mistake @worried-painter-31382!

No worries, I've mostly been hacking 🤓 If my contributions/design is the path forward, I believe using turbopack is not mutually exclusive with pants in a JS supporting world

@melodic-exabyte-60253 I should also point out that the current idea is to delegate to the existing JS/TS tools where possible, rather than come up with an N+1 solution. So, that could mean calling out to Turborepo (or Vite) in my case, as needed - but keeping the overall dev process the same for users.

Hi! I’m Louie. I previously worked at Twitter, so I was familiar with pants v1 but still new to pants v2. I’m starting a new side project which is based on python env, so pants naturally become the build system I picked. so far I’m pretty enjoy the pants v2, I may throw some questions around CI/CD integration with pants, so bear with me 😬 Nice to join the community here! 🙌

Terrific! By the way there is a section of the website that addresses using Pants in CI. It's a good starting point. Feel free to ask questions as well. We aim to maintain a responsive atmosphere. :⁠-⁠)

@busy-vase-39202 Indeed, I did see on the Pants website that you were looking for a partner for JS support. I think at the moment we do not (yet) have the capacity to handle this task, but that might change in the future and I would be interested in pursuing that task as it would make formatting & building our applications much more homogeneous. @wide-midnight-78598 & @worried-painter-31382: That's cool to know that you had already started the work on this. I think it makes the most sense to integrate with existing tooling as I don't see the point of reinventing the wheel. I might do some experiments to see how much work it would be to call out to a build system like Turborepo into Pants, but I want to get most of the Python setup out of the way first so that our team can be productive with Pants.