-
Notifications
You must be signed in to change notification settings - Fork 2
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
Service not found Exception #24
Comments
Hello @khastick / @jlcharette: quick question - in your composer.json file, do you use the https://github.com/drupalwxt/composer-extdeps composer repository or do you have explicit entries for the wet-boew package? |
@zachomedia I did not add any kind of manual entries in the composer file. Simply started by installing wxt_bootstrap with After adding the https://github.com/drupalwxt/composer-extdeps to my composer file, I was able to install the dependencies. Maybe updating the installation section in the readme would help understand that this manual step is required before installing wxt_library. Thank you for the help. |
@jlcharette Great, glad that worked. I agree, I'll get a note added to installation section in the readme. @khastick Let me know if adding the repository also fixes the issue for you. |
After running composer require drupal/wxt_bootstrap and installing and setting to default WxT Bootstrap 8.x-6.1 theme I receive the following error:
Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: You have requested a non-existent service "wxt_library.service_wxt". in Drupal\Component\DependencyInjection\Container->get() (line 156 of core/lib/Drupal/Component/DependencyInjection/Container.php).
I tried to run composer require drupal/wxt_library and received the following error:
Problem 1
- Root composer.json requires drupal/wxt_library ^6.0 -> satisfiable by drupal/wxt_library[6.0.0].
- drupal/wxt_library 6.0.0 requires wet-boew/wet-boew 4.0.43.1 -> could not be found in any version, there may be a typo in the package name.
The text was updated successfully, but these errors were encountered: