16

Why does node-sass have such garbage documentation?!
I've now spent over an hour trying to get a clear and concise answer to how that shit works, and what do I get? This: (see picture)

I don't know what any of that means, nor do they care to tell me.
I don't want to render this shit at runtime, I want it to compile the sass code when I make changes to it so my app doesn't get boggled down by unnecessary background processes.
But nooo of course not.
To top it off, the "easy" electron-compile solution doesn't even fucking compile because all its dependencies are either outdated or 404 on me. 😡

It's shit like this that makes me hate web-style development. Lacking documentation and people who just assume everything is logical and clear from the start. It's fucking not.

Comments
  • 4
    I think what scares me most about this ecosystem is that people build production systems on some of these components. Someone, at some time, has figured it out (miraculously) and included it in their code to fulfil some requirement. Then that person either leaves or is unavailable, the solution breaks and there's no docs to help anyone figure out why. Maintenance man days down the tubes just to be hip, trendy (and dare I say it, lazy).
  • 0
    @samk If its any consultation that'll happen in any complex system.
  • 0
    I know how you feel. I experienced the same and I was wondering if the problem was a lack in my preparation or the system just sucking. I'm like in the dark and it's difficult to move around, you can only touch and taste everything until you understand that it was what you wanted.
    ++1, you need a stressball
  • 1
    @crisz I already have one. And I've used it so much the :/ graphic has worn off 😅
Add Comment