8
puerto
7y

Babel and webpack kicked my ass today. fuck you babel, and fuck u too webpack. neither one of u fucks is making my life any better at the moment. things were moving along, now my app just looks like this. something in this transpile garbage. I'm not missing '>' . it's just not transpiling correctly I think.

Comments
  • 1
    As long as I need to transpile for ES6 and up ill continue to write ES5 😂
  • 1
    ES7 spread is so nice tho
  • 1
    that one tag

    Bagofdicks
  • 2
    Don't worry you will figure it out. Just simplify your configuration and make no assumptions about how it should work lol
  • 0
    and it wasn't really babel after all. I had screwed with my public path to my app.js (react router) in webpack. but the transpiler seemed to not be transpiling. smh. that was half a day there. jeezus.
  • 1
    @puerto I feel your pain. I just spent a week on building an npm package using webpack2 to bundle my production build. If you want to check out example config files I'm @fitzk on github. My react-tilecard project's webpack files are in working order haha ( for now ;) )
  • 0
    @reduxtris thanks reduxtris. I'm still stuck on hot loading so maybe I will.
  • 1
    @puerto for hotloading look at react-tilecard/example :) it's a little different with the latest version of react hot loader.
Add Comment