Tomorrow (Wednesday, April 25), I’m leading a Birds of a Feather (BoF) at DrupalCon Baltimore titled Managing Drupal sites with Composer (3:45 – 4:45 p.m. in room 305).
I’ve built four Drupal 8 websites now, and for each site, I have battle scars from working with Composer (read my Tips for Managing Drupal 8 projects with Composer ). Even some of the tools that I use alongside composer—for project scaffolding, managing dependencies, patching things, etc.—have changed quite a bit over the past year.
As more and more Drupal developers adopt a Composer workflow for Drupal, we are solving some of the most painful problems.
- Should I use the
composer.jsonthat’s included with Drupal core? If so, why is there also a
.lockfile included? (See issue: Improve instructions for updating composer.json and /vendor ).
- I just installed Webform and now it’s yelling at me about front-end libraries. How do I install front-end libraries with Composer, especially if they’re not on Packagist ?
- What’s the best way (or ways ) to set up your Drupal project using Composer? (See discussions about this on Drupal.org: 1 , 2 , 3 ).
- Is it a best practice to commit the
vendordirectory or not? Why?
- Sometimes I see tildes (
~), other times
^, and sometimes Composer yells at me when I try to add a module that has a beta release. Why is this stuff so confusing? I just want to add a module!
- I download tarballs or zip files of modules and drag them into my codebase. What’s the best way to install modules like Search API Solr or Address , when they require Composer?
Some of these questions have answers. Some are still being debated on a daily basis!
I’d love to see you come to the BoF tomorrow if you’re at DrupalCon, and you want to talk about Composer and Drupal. I’ll try to take notes and post them on my blog as well.