Web developper senior at Aspremont

Member Since 3 Years Ago

Experience Points

4,840 experience to go until the next level!

In case you were wondering, you earn Laracasts experience when you:

  • Complete a lesson — 100pts
  • Create a forum thread — 50pts
  • Reply to a thread — 10pts
  • Leave a reply that is liked — 50pts
  • Receive a "Best Reply" award — 500pts
Lessons Completed
Best Reply Awards
Best Reply
  • start your engines Created with Sketch.

    Start Your Engines

    Earned once you have completed your first Laracasts lesson.

  • first-thousand Created with Sketch.

    First Thousand

    Earned once you have earned your first 1000 experience points.

  • 1-year Created with Sketch.

    One Year Member

    Earned when you have been with Laracasts for 1 year.

  • 2-years Created with Sketch.

    Two Year Member

    Earned when you have been with Laracasts for 2 years.

  • 3-years Created with Sketch.

    Three Year Member

    Earned when you have been with Laracasts for 3 years.

  • 4-years Created with Sketch.

    Four Year Member

    Earned when you have been with Laracasts for 4 years.

  • 5-years Created with Sketch.

    Five Year Member

    Earned when you have been with Laracasts for 5 years.

  • school-in-session Created with Sketch.

    School In Session

    Earned when at least one Laracasts series has been fully completed.

  • welcome-newcomer Created with Sketch.

    Welcome To The Community

    Earned after your first post on the Laracasts forum.

  • full-time-student Created with Sketch.

    Full Time Learner

    Earned once 100 Laracasts lessons have been completed.

  • pay-it-forward Created with Sketch.

    Pay It Forward

    Earned once you receive your first "Best Reply" award on the Laracasts forum.

  • subscriber Created with Sketch.


    Earned if you are a paying Laracasts subscriber.

  • lifer Created with Sketch.


    Earned if you have a lifetime subscription to Laracasts.

  • evangelist Created with Sketch.

    Laracasts Evangelist

    Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.

  • chatty-cathy Created with Sketch.

    Chatty Cathy

    Earned once you have achieved 500 forum replies.

  • lara-veteran Created with Sketch.

    Laracasts Veteran

    Earned once your experience points passes 100,000.

  • 10k-strong Created with Sketch.

    Ten Thousand Strong

    Earned once your experience points hits 10,000.

  • lara-master Created with Sketch.

    Laracasts Master

    Earned once 1000 Laracasts lessons have been completed.

  • laracasts-tutor Created with Sketch.

    Laracasts Tutor

    Earned once your "Best Reply" award count is 100 or more.

  • laracasts-sensei Created with Sketch.

    Laracasts Sensei

    Earned once your experience points passes 1 million.

  • top-50 Created with Sketch.

    Top 50

    Earned once your experience points ranks in the top 50 of all Laracasts users.

  • Community Pillar

    Earned once your experience points ranks in the top 10 of all Laracasts users.

Level 6
25,160 XP
2 months ago
Activity icon

Replied to How To Debug Npm Run Watch ?

Thanks for your answer. I will try that.

2 months ago
Activity icon

Started a new Conversation How To Debug Npm Run Watch ?

Hello there ! Hope you are doing well !

My problem is fairly simple but I'm too noob to handle it properly.

I'm using laravel mix and npm run watch to build my css. The build is good (no error displayed, css update occur), then the watch stop watching.

By far for me npm run dev is the same as npm run watch . On another project npm run watch is coninously updating my css during dev ... but on this project ... it does not want to really watch.

My question is : where to look to find who is bullying npm run watch ?


const mix = require('laravel-mix');

mix.js("resources/js/app.js", "public/js/app.js")
    .sass("resources/sass/app.scss", "public/css");

mix.minify('public/js/app.js', 'public/css/app.css');


    "private": true,
    "scripts": {
        "dev": "npm run development",
        "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
        "watch": "npm run development --watch",
        "watch-poll": "npm run watch --watch-poll",
        "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",
        "prod": "npm run production",
        "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
    "devDependencies": {
        "axios": "^0.19",
        "bootstrap": "^4.5.3",
        "cross-env": "^5.1",
        "jquery": "^3.5.1",
        "laravel-mix": "^5.0.7",
        "lodash": "^4.17.20",
        "popper.js": "^1.12",
        "resolve-url-loader": "^3.1.2",
        "sass": "^1.28.0",
        "sass-loader": "^8.0.0",
        "vue-template-compiler": "^2.6.12"
    "dependencies": {
        "@fortawesome/fontawesome-free": "^5.15.1",
        "jquery-ui": "^1.12.1"

2 months ago
Activity icon

Replied to Running Tests Get Uncaught Illuminate\Contracts\Container\BindingResolutionException

Hello I met the same problem today and I still have no solution. All was fine between phpunit 9, laravel 7 and me when suddenly, whatever the test I'm running, it brings me an error

PHPUnit 9.3.7 by Sebastian Bergmann and contributors.

.                                                                   1 / 1 (100%)
Fatal error: Uncaught Illuminate\Contracts\Container\BindingResolutionException: Target [Illuminate\Contracts\Debug\ExceptionHandler] is not instantiable. in /app/vendor/laravel/framework/src/Illuminate/Container/Container.php:1017
Stack trace:
#0 /app/vendor/laravel/framework/src/Illuminate/Container/Container.php(818): Illuminate\Container\Container->notInstantiable('Illuminate\Cont...')
#1 /app/vendor/laravel/framework/src/Illuminate/Container/Container.php(691): Illuminate\Container\Container->build('Illuminate\Cont...')
#2 /app/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(796): Illuminate\Container\Container->resolve('Illuminate\Cont...', Array, true)
#3 /app/vendor/laravel/framework/src/Illuminate/Container/Container.php(637): Illuminate\Foundation\Application->resolve('Illuminate\Cont...', Array)
#4 /app/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(781): Illuminate\Container\Container->make('Illuminate\Cont...', Array)
#5 /app/vendor/laravel/framework/src/Illuminate/ in /app/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 1017

problem is I don't know what is bringing me this error. Test is green. Error is kind of very generic and I have no stack trace to investigate on. I should tell that I tried composer dumpautoload, I tried to rollback to a previous version of the code, all that with no success.

My problem is How can debug this ?

4 months ago
Activity icon

Replied to (Laravel) Multi Domain Route Testing Fail

Thanks. I failed to read this part...

So I rewrite some stuff .env



Route::domain('www.' . config('app.domain'))->group(function () {
    Route::get('/', '[email protected]')->name('www.index');

Route::domain('app.' . config('app.domain'))->group(function () {
    Route::get('/', '[email protected]')->name('app.home');

And we (browser + phpunit) are all happy. Thanks :)

Activity icon

Started a new Conversation (Laravel) Multi Domain Route Testing Fail


I've one problem with my testing on laravel. I'm handling 2 domains with the same laravel app. One is the main app, the other is the index page.




Route::domain(env('WWW_DOMAIN'))->group(function () {
    Route::get('/', '[email protected]')->name('www.index');

Route::domain(env('APP_DOMAIN'))->group(function () {
    Route::get('/', '[email protected]')->name('app.home');

On the browser side, no problem. When I'm trying to write a test that is checking everyone may access the www.index and only authenticated users may access app.home. Randomly it fails.

I obtain either :

  • Response status code [500] (if I dump it I see the app.home html code) I should get the www.index html code. Sometimes it works fine ...
  • on my production server I get
1) Tests\Feature\IndexAccessTest::testEveryoneIsAllowed
Symfony\Component\Routing\Exception\RouteNotFoundException: Route [www.index] not defined.

Again, on the browser side everything is good and the artisan route:list is listing the www.index route.

Here is my test


namespace Tests\Feature;

use Tests\TestCase;

class IndexAccessTest extends TestCase
    public function testEveryoneIsAllowed()
                'Get started free',

Please tell me I'm doing something really really bad. Thanks