rusackas commented on issue #32741: URL: https://github.com/apache/superset/issues/32741#issuecomment-2737068569
Thank you for kicking this off! I definitely support simplification and ridding ourselves of `lerna`! One thing I've been wondering about (which we should consider as an alternative) would be using`yarn` (on v4 at the moment). It's also pretty fast/clean/easy, and works with `changesets` as well, and supports workspaces and publishing. We might want to add it to the "alternatives" section for good measure. One thing I've been enjoying lately about `yarn` is the `overrides` capabilities it offers over `npm`, to help keep subdependencies free from CVE exposure. It sounds like `pnpm` has nearly identical capabilities, so that's cool. It even cleans up after itself when the top-level dependency no longer needs the override. I was GPT-ing again, and weighing pros and cons: <img width="771" alt="Image" src="https://github.com/user-attachments/assets/af301a9a-8339-40a0-b81d-66c870fb817b"; /> I did a little digging on the "Cross-Project Linking" aspects, and it does sound like `pnpm` will be an excellent fit for working with our monorepo packages, as well as developing (and migrating) monorepo pieces around as we work toward our new extensions architecture. I believe I'll be a +1 on this... let me know if you want help moving it forward with discussion/voting. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
