Member Since 9 Months Ago

Experience Points 2,350
Experience Level 1

2,650 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 23
Best Reply Awards 0
Best Reply
  • start-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-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-token Created with Sketch.


    Earned if you are a paying Laracasts subscriber.

  • lifer-token Created with Sketch.


    Earned if you have a lifetime subscription to Laracasts.

  • lara-evanghelist 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.

24 Jun
3 weeks ago

ryssbowh started a new conversation Mix And Module Architecture

Hi all,

Looking for advices for a problem I've been having for quite some time now, hope somebody can share some lights on this :

I'm trying to build an application that has several modules (thanks to https://nwidart.com/laravel-modules/v4/introduction) in their own folder, and themes, in their own folders too. Each of those define js and css that can be included at runtime or not (if the module/theme isn't used for that application/route). So far I had one webpack file for each module/theme and a root webpack file including them all and building the assets into the public directory, one file per module/theme, and the module/theme responsible for loading their assets at runtime. I had a command to merge all package.json and libraries were shared in the root node_modules folder.

It works ok in development but I'd like to take it a step further and automatize the thing so I can add modules/themes (through an UI or composer or whatever) without having to rebuild assets locally.

I could have my assets already compiled in each theme/module but then it would mean having the module's assets being compiled without any knowledge of other modules, it would make sense I suppose, but I loose the ability to extract whatever external libraries a module could use. What if I have 2 modules/themes that require the same external library ? this library would be loaded 2 times, it doesn't work either.

So should I look at building assets on the spot when a module is added (through php, is that possible ?). Each module would have its node dependencies copied at development in its folder. Does that sound possible/logical ? Or am I just dreaming here and I do have to load a library two times if two modules need it ? Or anything else I could look at ?

Thanks a lot for your time.