12

Sick and fucking tired of this bullshit.
Previously worked with Laravel, used 'gulp watch' to watch for changes in assets and now they changed things for the better of Laravel Mix as a fucking wrapper for webpack. Now I have to do shit load more stuff to get gulp working, 'cause otherwise my 'npm run watch' shits itself every fucking time I run that shit, doesn't matter what fix is aplied. Battling that bullshit for 3 days now and shit's not working anyhow. Stupid fucking bullshit. Sorry, had to let it out from myself.

Comments
  • 0
    Whats wrong with it? I have no issues with running npm run watch. :/
  • 0
    @surgiie I always get "Failed at dev script bla-fucking-blabla...".
    Node with npm - latest, homestead - latest, cross-env is added to laravel mix and altered. Jefrrey Way says it's about updating node and npm.
    Did all of that, nothing change... it was the only spare time for me to do coding and not focus on uni and here we fucking go. Just planted all my assets in public dir and Bob's my uncle. Fuck that bullshit. Too irritated to tell something else.
  • 0
    I guess i had the same problem you are encountering. I know this isnt SO but can you show me the error message? Maybe i can help.
  • 0
    @Jackowski Read something that it might be the issue of not referencing the right npm...thing.
    I dunno, don't know shit about npm, node or some package manager like that.
  • 0
    Fuck, I haven't got that stupid fucking config there. Brb
  • 0
    @Jackowski Update: had to revisit laravel on github and copy the package.json file from there (was quite different in respect to commands). npm run watch and preceeding npm run dev works now.
  • 0
    @dirtycasual Nice! I knew that was the problem it ocurred to me yesterday or something.
  • 0
    @Jackowski Yet somehow strange from npm's side... glad we are both up and running now!
  • 0
    I had to battle it for a few days as well but I am not too good with npm. After updating node, npm and digging a bit in GitHub issue pages I got it working.

    Could someone help me understand the difference between mix.js() and mix.scripts()?

    The first one seems to include a ton of other code as well.

    All I need to do in my project is include jQuery and file with 15 lines of jQuery code. Isn't all this overkill?
  • 0
    I built my own webpack. It's far superior. Mix, yet another layer of madness ontop of a layer of madness. Just did my own project, everything's clean and crisp. Just tried to build a laravel project with mix, 2 minutes to build on a massive workstation, 10 minutes + on a modest computer. Are you kidding me? By default mix is burying all info needed to know WTF is going on to spend 10 minutes building assets and 10MB of js/css on a brand new project.
Add Comment