r/javascript • • Nov 30 '16

Modern JS developer workflow makes me sad

Edit:

Wow, I would never have expected so many replies and advises. I sincerely thank you all!

I would like to highlight 3 tips that have helped me the most:

  • @sdihgusdoiu - Hard Source Webpack Plugin. This plugin was rarely given a mention in other links given what a difference it makes and how simple it is to set up compared to other solutions.
    My mental model: it calculates a hash for Webpack config and package.json. If neither a compilation unit nor the hashes changed, it reuses output of previous builds for that compilation unit.
    This results in a massive decrease in (re)build times. ~70s build became ~5s.
    I wish this would be built into Webpack itself, although I understand there are reasons why not.  
     

  • @acemarke - Definitely a subjective hint that many people will dislike: Use eval for source maps in Webpack
    Not only is it by far the fastest option for Webpack to produce, the source it emits is what the browser actually executes. No more brain-dead breakpoint jumps by Dev Tools. Now you are free to copy-paste and play around with code directly from the Dev Tools.
    Yes, it does show an ugly transpiled code instead of your beautified ES6 + JSX, but it sounds much worse than it really is. Much more reliable and predictable than inline-source-map.  
     

  • @Retsam19 - for frequently used modules consider exporting them as globals using Expose loader
    Being able to dynamically REPL require(modulePath) for any module seems not to be possible, although there are some Stack Overflow answers claiming it is. I couldn't get them working
     


Original Post:

This post is partly a rant, partly a cry for help, partly an inquiry about any tips and tricks that could improve our day-to-day work.

My company adopted a new, modern JS stack; all pretty standard:

  • React

  • Babel ES6 + JSX

  • Redux

  • Mocha

  • Webpack

  • React Router

  • lodash

  • along with their 1262 transitive dependencies (I'm not kidding here!)

As a result, my daily productivity plummeted. Honestly, I feel like x86 Assembly must have a friendlier set of developer tools.

A non-exhaustive list of issues:

  • We used to laugh at Java guys with their sluggish Maven, at C++ compilation times.
    Nowadays it takes Webpack longer to build a todo app than for a complex Java project to download all dependencies, clean project, compile all files, run all tests, create a package and upload it to repository. npm is even worse

  • So...Webpack's hot reload, the mythical feature getting universal praise.
    Apart from the fact that "hot" means "after 5 or more seconds", it comes with the worst of both worlds - sometimes it does work, sometimes it just doesn't; with no indication whatsoever whether it succeeded or not. So you spend 2 minutes figuring out why your fix didn't work, only to find out it hasn't been deployed in the first place. A colleague of mine stated: "I just don't trust hot reload. I always reload the entire page"

  • Webpack or Babel or something comes with a special, depression inducing feature: if you make a syntax error in your file, instead of displaying a clear error, it loads some random cached build from half a day ago

  • my employer can definitely find a better use for its money than me tracing build bugs of some deeply nested transitive 3rd party library that whimsically has changed it's AMD/UMD exports

  • so...source maps. I can see my original sources in Developer Tools! Usually, that is. So, let's try to add a debug breakpoint to my code!
    If you are lucky, it will stay on the line you clicked. Other times, it jumps a few lines up or down. Occasionally, it jumps to the bottom of the file. When developer tools sense that you haven't been frustrated for full 10 minutes, the breakpoint jumps to a 200kLoC app.js file, which freezes the entire Dev Tools and Chrome with it. Now, don't close Chrome at this point! If you do so, the next time you open Dev Tools, it will try to reopen the last session and freeze again. Just wait patiently for 2 minutes till Dev Tools finishes parsing the file, grab a cup of coffee. Actually, an antidepressant might be a better choice.

  • you won a lottery and Dev Tools really did stop at your breakpoint. Congrats,. Now, let's inspect some expression. Uncaught ReferenceError: X is not defined. What? Well, Babel thinks the best way to compile this piece of code:
    moment.isDate(...)
    is to translate it to:
    _moment2.default.isDate(...)
    This is done to every ES6 import. And yes, that "2" in _moment2 can and will change to "3" or just disappear, at any point.

  • Let's write some tests. Hm...they failed, let's see what's happening. Well, Chrome executes your test before it loads your sourcemaps, so it totally ignores your breakpoints. Remember that 200kLoC app.js file? That's your best bet now.

  • One of the best features of Javascript was an interactive REPL console in the browser. But that's so 2014! With Webpack/Babel, it's just not possible to get a reference to a particular module from Dev Tools Console. By design. Because best practices, man!

  • On the other hand, we have the 8th Wonder of the World, a time-travelling debugger for Redux. Last time I productively used it was never.

 

Is this...normal?  

How do you cope it?  

How is this clusterfuck touted as a state of the art in Javascript?  

Did you also become alergic to the phrase

makes it easy to reason about

 

516 Upvotes

292 comments sorted by

View all comments

Show parent comments

6

u/lhorie Nov 30 '16

I actually lived through Scriptaculous, IE6 bugs, VB scripts to make Flash talk to JS, and a lot of that old school insanity, and honestly, it was fun. You'd have to learn all these unspeakable hacks but you'd come out at the end of the day with something to show to the client. The state of affairs was bizarre but it was fairly stable for a good few years before jQuery became a thing (and it was fairly stable for a few years after that too), so you could accumulate knowledge and actually level up your IE slaying skills.

The problem these days is that you get a lot of "eh I spent 20 hrs trying to get HMR working, I'll figure out how to configure it properly later"... and 10 months later, it's a mess of half a dozen half-ass-configured things and poorly understood infrastructure. It's largely self-inflicted code debt, but it's difficult to justify spending time on these things to a client. And instead of ever investing the time to learn a tool properly like you'd do in most other programming languages, a lot of times the go-to "solution" that people reach for is "eh, I'll try this other thing I saw on Reddit 3 days ago"

The shift is essentially that the old suckiness was a technical problem that could be overcome w/ craftsmanship, but today's suckiness is largely a social problem that is a product of coming into programming with a consumerist, impulsive shopping mentality.

7

u/themaincop Nov 30 '16

Maybe the new ecosystems make life worse for people who treat programming like impulse shopping, but for those of us who actually do enjoy the craftsmanship aspect of it, things have never been better. If you actually take the time to learn what webpack is doing (which really doesn't take long) you get access to a ton of tools that make life easier and allow you to build bigger and more complex things.

I think you're wearing rose colored glasses if you somehow think that spending a day debugging obtuse errors from IE6 was better or more productive than tinkering with your dev environment.

5

u/lhorie Dec 01 '16 edited Dec 01 '16

I think you're wearing rose colored glasses

Maybe. Personally I did feel more productive debugging obtuse errors back then than I do tinkering w/ dev environments now. Don't get me wrong, tinkering w/ dev ergonomics can be fun, but I feel that all that tinkering detracts from actually doing meaningful work. But to each their own.

re: Webpack - it itself isn't bad, and I can make it do what I need just fine. The problem is what I said earlier, of someone in your team going to town with random plugins on top of a random boilerplate when the deadline is in a month, and then nobody has time to continue arguing why that was a bad idea, nor time to fix the source maps, or figure out why HMR is being dog slow or why some other thing is broken in some annoying but not completely showstopper way

1

u/sittingprettyin Dec 01 '16

That consumerist mentality thing is a great way to phrase that. Just look at the attention library makers put into their goddamned logos for full confirmation there.