3 ms·
I don't know whether the path is the problem that makes modern web dev so hard to learn. I'm currently trying to setup the js testing library "jest" to use bab
by Gehinnn 6y ago
I don't know whether the path is the problem that makes modern web dev so hard to learn.
I'm currently trying to setup the js testing library "jest" to use babel to transpile typescript and I get the most obscure error messages. This is painfully hard and I have years of experience with javascript/typescript [1].
I doubt there ever has been a more complex programming ecosystem than JavaScript's.
No other system has more bundlers (webpack, rollup, metro, ..), transpilers (babel, typescript, flow, ...), testing libraries (jest, mocha, jasmine, ...), package managers (yarn, npm, pnpm, ...).
It is just insane what we created.
[1] if you are curious, that is the error message. Good luck making sense of it. It probably is caused by non-compatible dependencies but yarn does not tell me.
Validation Error:
Preset @babel/preset-typescript is invalid:
The "id" argument must be of type string. Received type object
TypeError [ERR_INVALID_ARG_TYPE]: The "id" argument must be of type string. Received type object
- toomanybeersies 6y agoI had to do a take home programming task over a weekend for a job interview last year, the only technical requirement was that it had to be done in JS (both Node and browser). It had been a few years since I had started a JS project from scratch (I spend 90% of my time doing Rails dev). I ended up spending more time figuring out what package/build/testing tools to use than I did actually writing code. Looking up best practices for Express.js project structures, I found that every blog post/article had a different "best" structure. I'm happy that my new job is still primarily Rails. I'll take convention over configuration any day.