Last night I nearly finished my portfolio site. I was working on the perfect framework and workflow like forever. But in the end I accomplished a pretty pleasing solutions. For the back-end I choose Laravel with it's built in rest-api, the front-end is managed by Vue. I'm also proud of my assets-management which is handled by Gulp + Webpack (Laravel Mix). But here I decided to run Gulp on images, fonts and CSS and let Webpack bundle the JavaScript.

And what really crawls my balls is that I can write Sass and Jade, even use partials and organized the shit out of this website, and let Gulp just vomit some minified HTML and CSS on the other end.

Man that feels so good.

Right, that's fucking it. Enough. I'm all for learning new technologies, frameworks, and development protocols, but my time on this earth is limited and at the end of the day if I'm having to spend DAYS AND FUCKING DAYS just scouring through obscure forum posts because the documentation is shit and just hitting ONE FUCKING PROBLEM AFTER ANOTHER then there comes a point at which the time investment simply isn't worth it. I HATE throwing in the towel because some FUCKING CUNT code problem has got the better of me, but fucking sense must prevail here.

Laravel fucking Mix. Do any any of you use this shit on Windows? Because I take my fucking hat off to you. I'm done with it.

Oh, so your server uses 'public_html' instead of 'public' does it? Well, of course you can just set

mix.setPublicPath('public_html'); then can't you?

No, you can't. Why? Because fuck you, that's why. Not only do you have to hard-code your fucking public directory into each specified path, additionally you have to set

mix.setPublicPath('./');

Why? Because fuck you, that's why. It took me the best part of two days to discover that little nugget of information, buried at the bottom of some obscure corner of the internet in a random github issue thread. Fuck off.

Onto next problem. Another 5 hours invested to extract some patchy solution that I'm not at all happy with.

Rinse, repeat.

Make it work with BrowserSync by wrapping your assets like so:

<link rel="stylesheet" href="{{ mix('/build/css/main.css') }}">

Oh oh oh but "The Mix manifest does not exist"... despite a fresh install of Laravel 5.6 and all relevant node modules installed... follow some other random Github thread with a back and forth of time-consuming suggestions for avenues of experimentation, with no clear solution.

Er no, fuck off. I'm going back to Grunt and maybe I'll try Webpack/Mix in another year or two when there's actually some clear answers, but as it stands this a wild goose chase into a fucking black-hole and I've got better things to do with my precious time. Go die.

I'm curious, why did they rename Laravel Elixir to Laravel Mix?

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.

What a fucking retarded dickhead the laravel creator is, after having multiple hours/days of checking and asking people, we figured out, that apparently you cant mix variablenames in lumen afterall (like the docs are saying), so either you stick with the same variablenames you have in your route, make them all something different or you get fucked by random variables taking dominance and replacing the order completely. You'd think one can just make a PR to the docs on github and submit as much information as possible and it'll be fixed, right? no, you cant, that fucking blown balloony retard just closes it immediately with the notice of "I believe this is already noted in docs" - although it isn't thats the whole point you fucking blow up doll, how the fuck are people supposed to know your piece of shit will fuck the order completely, just because of one thing that isn't mentioned anywhere!

I’m on a laravel project which is going great, the ass rapping part of it is compiling this fucking sass with laravel fucking mix... fuck it I’m setting up gulp

So let me get this straight.
- You propose a tutorial about how to create an e-commerce website using Laravel, with a shitty powerpoint-like display
- We have to click "next" to learn the basics of PHP, MVC, Laravel, Mix and such, while all I need to know is about the payment system and global logic
- On the last PowerPoint, you suddenly decide that you should finally think about displaying some actual code while all before was theoric class
- So the last powerpoint page is 45 times longer than any other previous pages.

- Of course, there was nothing about what I was looking for.

You should consider stop wasting everyone's time as a 2018 new resolution.

VSCode for Laravel sucks. Blade is totally broken. If you know good plugin with emmet support and blade highlighting together, let me know. Also Laravel Mix is a little bit trashy and buggy with Pug :P

What a fucking pain to setup WYSIWYG in Vue with Laravel fucking Mix. I want to kill myself.

So this is really a thing. I'm used to have yarn build/dist/watch and serve commands but my collage is used to laravel mix, and we working with static URLs like client.local. I'm used to localhost:xxxx which is better because you can use hmr. So what do you guys name your development build command and the one for production?? convention

Good job Laravel Mix!