Watch: Wordpress trac discussion on Composer's inclusion.

[mmorris8]

Creating this as dev and maintainer's heads up of a relevant discussion in the Wordpress trac I've joined.

https://core.trac.wordpress.org/ticket/47256

Composer's direct incorporation into WordPress core has ramifications for the next version of Timber. In particularly, I've drafted out a hooks implementation in package.json and raised the issues known to me that will be faced.

I would appreciate feeback from the maintainers here on that thread as Timber is the most extensive Composer dependent yet WordPress specific library I know of (and I'm glad it exists). I'd like to see a day where I can ship a plugin or theme with timber as a declared dependency and it just work for anyone wanting to install them.

[nlemoine]

Hi @mmorris8,

Thanks for bringing this ticket to our attention. From what I understand, the discussion is mostly around using Composer to pull WP core dependencies, not as a package manager intended for the entire ecosystem. I may have missed something but I can't see how this would affect Timber or any other WP/Composer based library.

Just like you, I would love such move to realize but I honestly think this will probably never happen within a near future (I've seen trivial trac tickets closed 10 years after opening). Wiring Composer at WP scale would raise an infinite number of challenges I can't even think of.

That said, developers that want Composer already have plenty of options available: Bedrock, WPStarter, etc for the stack, WP Packages to consume themes or plugins. It's just different ways to consume WP. And that's currently fine.