I was going to write an obligatory "fuck webpack" post but decided to skip it and try out rollup.


..and they said it would be better than webpack.
The more things change the more they stay the same.

At this rate maybe I'll just join the military and kill brown people in the middle east for a living.

  • 3
    TBH I do need a fucking bullet in my brain dude 🤣. Seriously fuck webpack
  • 2

    You know how to get jsx to play nice with rollup without 50 fucking lines of voodoo and a goat sacrifice?
  • 1
    @Wisecrack Holy shit 😂. Yea pretty much
  • 1
    It's supposed to be useful as a command line tool, but if you want to do anything even half unexpected you best be sure you MUST make an "optional" rollup config and put your dependencies in the right order.

    Which speaking of which, the examples that I've seen has numbered dependencies. So I take it they have to be locally installed, rather than grabbed from a repository e.x. npm?

    So whats the fucking point of having repositories to begin with?

    Also what the shit is commonjs? I thought the WHOLE FUCKING *POINT* of bundlers was so we could avoid shit like that?
  • 3
    I choked on air reading "kill brown people". What an amazing job description: I kill all kinds of people but I specialize in killing the brown ones.
  • 0

    Such is life.

    What do you do for a living?
  • 1
    @Wisecrack if I remember right the rollup documentation makes it sound way more complicated that it is. I think I spent an hour or so trying to figure out what options I needed to pass it to preprocess a less stylesheet only to find that I didn't need any and I had spent all that time looking for nothing.
  • 0
    @Wisecrack dont use jsx lol but seriously webpack is awful but ive had good luck with rollup
  • 0

    Don't use jsx?

  • 0
    @Wisecrack i know its very popular but just my preference i’m really not a fan
  • 1

    From looking at it im not a fan either. But i'm an ignorant junior, so what do I know?

    Point is, lot of react devs use it, which means a lot of react jobs probably do to, which means I should probably be passingly familiar with it.

    Everyone focuses on language and techstake but dev skills seem to be the golden ticket: knowing semantic versioning (which seems dead simple for all the hype, took 5 minutes to learn), SQL, Git (well this is basic shit anyway), some sort of bundler/taskrunner/etc if you're doing frontend, etc.
Add Comment