Skip to content
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

LERN not auto-discovered in Laravel 5.5 #52

Closed
sroutier opened this issue Oct 31, 2017 · 3 comments · Fixed by #53
Closed

LERN not auto-discovered in Laravel 5.5 #52

sroutier opened this issue Oct 31, 2017 · 3 comments · Fixed by #53

Comments

@sroutier
Copy link
Contributor

Hello,

Anybody else having trouble getting LERN to get auto-discovered?

Here is the output of the require command from a fresh Laravel 5.5.19

$ composer require tylercd100/lern
Using version ^4.2 for tylercd100/lern
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 4 installs, 0 updates, 0 removals
  - Installing tylercd100/monolog-sms (1.3.0): Loading from cache
  - Installing tylercd100/monolog-mailgun (2.0.0): Loading from cache
  - Installing tylercd100/laravel-notify (2.1.0): Loading from cache
  - Installing tylercd100/lern (4.2.0): Loading from cache
tylercd100/laravel-notify suggests installing sentry/sentry (Required to use the Raven driver for Sentry (~1.7).)
Writing lock file
Generating optimized autoload files
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover
Discovered Package: fideloper/proxy
Discovered Package: laravel/tinker
Package manifest generated successfully.
$
@tylercd100
Copy link
Owner

I see the problem, I will patch it super quick!

@tylercd100
Copy link
Owner

@sroutier let me know if that worked for you

@sroutier
Copy link
Contributor Author

sroutier commented Nov 1, 2017

Works. Thank you.
/s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants