-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to install modules, for example upgrade_status for D10 compatibility #12
Comments
Note: for upgrade status to work from the UI, had to temporarily remove the symlink_project.php file from the module folder but that's off topic. |
If you need additional modules you add them to require-dev and rerun poser. Does that answer your need? |
Just giving feedback as I had to try this again and adding a contrib module with require-dev doesn't seem to work, unless I'm missing something, it still adds it in vendor. This is the composer.json I had to add in the module this time (drupal 10).
|
Just some notes of what I'm doing for this workflow.
The composer.json file is untouched after dev poser, but if you need additional modules, or upgrade/downgrade the drupal core version, all the stuff ends up in vendor.
This is what my composer.json looks like to install upgrade_status on D9:
The bits require are the composer/installers package together with the extra/installer-paths, and the repositories.
Maybe we could have a way to emulate what poser does with expand composer json (https://git.drupalcode.org/project/gitlab_templates/-/raw/1.0.x/scripts/expand_composer_json.php) to install a module or change the core version?
The text was updated successfully, but these errors were encountered: