Switching from "dev-develop" to stable 6.0

What do you have in your composer.json at the moment?

You should have this:

Update your laravel/framework dependency to ^6.0 in your composer.json file.

And then run composer update

And that's it? Because it did that automatically. But I'm a little confused as I'm still not using Ignition to present exceptions. That makes me wonder if there's anything else I'm missing...

@fogley Here the upgrade guide, you should check that out for recent changes.

And for ignition I guess you don't have it in your composer.json file. So based on the composer.json on the master branch you should add "facade/ignition": "^1.4" as a dev dependency.

Couldn't I just overwrite my current composer.json with the one from the master branch (https://raw.githubusercontent.com/laravel/laravel/master/composer.json) and then update with composer?

There shouldn't be anything to upgrade, right? - I've been running the 6.0 dev branch so far...

@fogley no, just take the required packages from there don't just override it. Because the composer.json file contains the name of the project, the project version and so on. You can create a new project instead and copy the composer.json from there if you really want to.

My composer.json is identical to a vanilla Laravel project... I'm just gonna create a new project and migrate my files manually.

So I just moved all the project-specific files to a brand new laravel project. Ignition is still not handling exceptions...

Is it not defualt yet?

It should be the default. But you should also take a look at the documentation my friend. I don't know why it does not work for you. Take a look [here])(https://flareapp.io/docs/ignition-for-laravel/installation) for installation.

If we assume that app/Exceptions/Handler.php should contain the function included in the guide you just linked to, then I can verify that installing Laravel 6.0 via Composer does not include that.

@fogley I just ran laravel new laravel6 and once all done in the default / route threw an exception using throw new Exception("Error Processing Request", 1); and I got the brand new Ignition page. So it is all good.

You are probably missing some dependencies or take a look in your IDE if you can open the IgnitionServiceProvider.

Make sure to run php artisan config:clear in order to clear the cached config files and run again.

I really appreciate the help, but...

I just cleared the Composer cache, and installed Laravel once again as per the official docs, via Composer. I still cannot see Ignition. This installation is completely vanilla. Running your piece of code does return an exception, but not through Ignition.

I'm giving up here...

I just updated last night, get the composer.json from:

https://github.com/laravel/laravel/tree/master

It has ignition.

For some reason they haven't put master on the stable release page yet.

Note .editorconfig has a change as well.

Here is the composer pr https://github.com/laravel/laravel/commit/13ab419d59e2f0d2e188a5157a3cc17f72db595c

@fogley and here Jeffrey's video on Ignition :)

So, I tried installing the dedicated Laravel installer globally via Composer (https://laravel.com/docs/6.0#installing-laravel) and that did the trick. Migrated my files and Bob's your uncle. Thanks everyone, for the input.

@fogley the same as I've shown you above did the trick but still you did it your way 😁

Look for:

laravel new laravel6

above in my replies.

Yeah, I know. That's why I ended up trying it. I just didn't realize that there would be any discrepancy between doing it the old way (composer create-project) and the dedicated installer (laravel new).

Isn't laravel new just a wrapper for Composer?