Is Shopify Getting Rid of Packwerk?

Tools Packwerk
1

This message was imported from the Ruby/Rails Modularity Slack server. Find more info in the import thread.

Message originally sent by slack user U71268WT64J

:wave: Hey everyone. Great to meet you.

I am working at bloomandwild.com - where we’ve been taking on Packwerk for a while. In a conversation with a friend over the weekend they said that “Shopify is getting rid of packwerk”… I was wondering if there’s any truth to this? I suspect that https://github.com/Shopify/packwerk#️-while-shopify-is-actively-using-packwerk-we-consider-it-feature-complete has misled them :slightly_smiling_face:

Some of the activity in https://github.com/Shopify/packwerk/discussions/221 and https://github.com/Shopify/packwerk/discussions/219 seems to indicate that it’s still used (and intended to be used) but some of the functionality in Packwerk doesn’t quite “fit”.

2

Your observations are spot on. Having spoken with a number of the folks working on this at shopify, I don’t come to a different conclusion

3

Message originally sent by slack user U70TIGAX94P

I don’t see a big change in opinion on the Shopify side there - these things are pretty much in line with packwerk‘s original goals. Privacy was always just a low hanging fruit that we could add on as an incentive for people to start using it, dependency management the main goal.

Removing privacy enforcement might sound dramatic but shouldn’t be seen as a change in intentions on Shopify side IMO. (I‘m no longer at Shopify but I talked about both of those threads with Rafael earlier this year)

Same with the „feature complete“ thing - it‘s been there for most of the time that packwerk was open source. We even made it a little less scary at some point. The main point is that Shopify didn’t intend to negotiate a barrage of feature requests, or disappoint people when those are rejected.