in

Getting more than you bargained for: removing a Drupal module with Composer

I have issues with Composer on two fronts. First, its output is extremely user-unfriendly, such as the long lists of impenetrable statements about dependencies that it produces when it tells you why it can’t make a change you request. Second, many Composer commands have unwanted side-effects, and these work against the practice that changes to your codebase should be as simple as possible for the sake of developer sanity, testing, and user acceptance.

What do you think?

0 points
Upvote Downvote

Leave a Reply

How to Convert Existing Blog Posts to Gutenberg

How to Test Your Site for Updating to Gutenberg (WordPress 5.0)