Add module dependencies to composer.json

Created on 6 December 2023, 7 months ago
Updated 9 January 2024, 6 months ago

Problem/Motivation

Generally speaking, it's a good idea for your module's composer.json to require its own dependencies. That way your single composer command gives you everything you need to be able to turn the module on.

Steps to reproduce

Spin up a DrupalPod instance from this issue. Note that the build breaks while trying to enable disclosure_menu because `token` (and `twig_tweak`) are missing.

Proposed resolution

Add the two projects (with necessary version constraints, if required) to the `require` section of `composer.json` and update the dependencies listed on the project's description.

Remaining tasks

- fix this issue
- test this issue
- update the project description

User interface changes

-none-

API changes

-none-

Data model changes

-none-

๐Ÿ› Bug report
Status

Fixed

Version

2.1

Component

Code

Created by

๐Ÿ‡บ๐Ÿ‡ธUnited States chrisfromredfin Portland, Maine

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.69.0 2024