-
Notifications
You must be signed in to change notification settings - Fork 83
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
Laravel dump-server does not log anything on console #34
Comments
you need to use the dump function not die and dump |
I've tired both dump() and dd(). It does not work either. |
@cosecantt what's your server setup? Are you using homestead/docker/valet? |
I am using following:
Upgraded from Laravel 5.5 to 5.6 and 5.6 to 5.7 following the upgrade manual on documentation |
Similar issue but with different setup. And I did use the
No output. |
Same issue using: Laravel Valet 2.1.1 it works however in laravel telescope but not with each request. |
@mpociot i am using it with docker? should it work out-of-the-box with it or i need to configure something |
i got this problem also... the real problem was i installed laravel telescope, went to the url and afterwards started dump-server... |
[STARLOG / entry / day 1028 - talking at the void] I've been out here so long that I actually miss the browserwars that made me leave earth in the first place. Anyways.. while gooogling I found this page and suddenly it hit me... an old familiar memory. I realised I am running all stuff in a virtual machine. Well.. mind you.. it's not that I didn't know.. I boot the damn thing everyday. It's more that coffee in deep-space works differently. It floats and you need to take bites out of it, then do gyro exercises hoping the coffee reaches your stomach. So since this ticket is still open and I type at least 35 WPM with a accuracy of at least 10%, I wanted to add this obvious fact: Start |
Laravel upgraded from 5.5->5.6 then 5.6-.5.7
I can run following command
shows following:
But
does not log on the console. Instead it shows on the browser.
The text was updated successfully, but these errors were encountered: