Handy guide to webpack:

1. Copy-paste stuff from internet until it works.

That's it!

Goddamn you rant a lot nowdays

2. Don't use webpack 😉

@Dacexi I was just about to say that...

Maybe need to Unsubscribe....

@billgates come on m8 it's hard to stop when I am working 24/7

@billgates but you should unsub me for a while if you are getting annoyed. I will let you know when I have cooled down 😋

@tahnik is your working 24/7 how do you have time to post rants.

Problem with Subs in general I think is I don't check the main feed much nowadays...

@tahnik yea guess I'm getting too much tahnik, need a bit more variety... No offense 😁

https://github.com/kenpeter/.... I need to understand each term deeper

Pretty much the entirety of my programming skill set right there. I suffer constantly from "what do I type next" syndrome.

Handy guide to front end:

Don't build it and tell end-users they can simply use their favorite command line http utility to request json objects.

Exactly what I did when my boss asked to implement webpack in our project ^^

Webpack is inspired by Git. Only the author understands it.

I was completely overwhelmed by webpack, so I cheated and used laravel-mix instead.

Its like a layer on top of webpack with simpler options. Good starting point, but I should learn webpack properly.

Webpack has a nice documentation. If you take the time to read it, you will know what you're doing.

The best way to learn webpack, even front end is that I need to understand each term in a deep level. Eg. What is entry? What is output? I will go through individual tutorial and YouTube and understand the fuck out of it. This way, i know exactly what I am doing.

@kenpeter wow, there is no coincidence.

My next task is to set up webpack for our custom cms

Thanks!