9 ms·
Node.js v9.2.0
- STRML 9y agoNot a lot of notable changes in here, but it's nice to see the v9 branch moving quickly. The sheer velocity of NodeJS - even now after all the ES6 features & async/await are finally available without flags - is something to behold. Looking forward to v10 once the churn has settled.
- deleted 9y ago[deleted]
- singularity2001 9y agoawait keyword not usable in repl yet? [without (async _=>{x=await wtf()})()]
- STRML 9y agoBare `await` (REPL-only) came in Chrome 62 - and it's on the way to Node soon. https://github.com/nodejs/node/pull/15566 https://github.com/nodejs/node/pull/15566
- deleted 9y ago[deleted]
- drinchev 9y agoNode.js and the community behind it are really great. It helped me put bread on my table for several years now. I remember I passed through all the "trends" around it and I'm super impressed how fast the ecosystem is evolving. From browserify to webpack, from grunt to gulp, from coffee-script to typescript. It's never been so exciting.
- beaconstudios 9y agonow all we need is a code-over-configuration replacement for webpack (like gulp was for grunt) and the build system will have evolved from a mess of JSON to a programmable compiler ecosystem. That's pretty cool.
- iamleppert 9y agohaven't you heard of browserify?
- beaconstudios 9y agoI have, but it's not what I'm talking about. See the comment above re. gulp.
- drinchev 9y agoI forgot to mention that these days most of the projects that I see use a combination of webpack and npm scripts. I guess gulp will be obsolete in the next years.
- rmrfrmrf 9y agoI still think Grunt and Gulp have a place outside of npm scripts for build automation, deployment, and automation of one-off tasks. The fact that Gulp is fully concurrent by default makes IO and environment setup lightning fast. With Electron cross-platform builds especially it takes a lot of the headache out of trying to shim every possible platform configuration into a one-liner.
- chatmasta 9y agoYou can write webpack “config” in JavaScript. It’s already programmable. Not to mention every loader is programmed... I’m really not sure what you’re getting at here.
- beaconstudios 9y agohave you used gulp? It allows you to code up a processing pipeline in a pretty intuitive way. Webpack, even though its config is written in JS, is basically magic JSON files. Gulp offers near-total control over the build process which also helps with optimising things like build speed.
- amigoingtodie 9y agoWhat is your current toolchain in the node ecosystem?
- drinchev 9y agoDepends on the project, mostly a combination between - npm scripts ( mocha, nyc, tsc, etc... ) - webpack - gulp
- Scarbutt 9y agoSerious question, why has nodejs become so ubiquitous in big companies (netflix, linkedin, walmart, trello, uber, paypal, medium, ebay, groupon, NASA) ? Is it because is the most practical option? like, there are no fast runtimes for dynamically-typed(for fast iteration) languages that also have big ecosystems and is well sponsored? Fast - rules out Python and Ruby. Dynamic - rules out Java, Scala and Go? Clojure - to awkward for most companies, small ecosystem but can call Java, JS. Lua - to niche. If you need to write a backend(frontend?) for a SPA with SSR(or no SSR) or WebApp why would chose something else besides nodejs (ignoring familiarity with other lang and hating on JS)?
- drinchev 9y agoAccording to google trends [1]. Golang seems more popular than nodejs. 1: https://trends.google.com/trends/explore?date=all&q=Node.js,golang https://trends.google.com/trends/explore?date=all&q=Node.js,...
- pledg 9y agoI only search for 'node' not 'node.js'
- Already__Taken 9y agoAnd node/nodejs outstrip golang https://trends.google.com/trends/explore?date=all&q=Node.js,golang,node,nodejs https://trends.google.com/trends/explore?date=all&q=Node.js,...
- kgthegreat 9y agoDifferent search terms give different trends: https://trends.google.com/trends/explore?date=all&q=node%20js,golang https://trends.google.com/trends/explore?date=all&q=node%20j...
- mhd 9y agoPeople thought that frontend skills transfer to the backend if you only use the same language (And sadly they did).
- Wintamute 9y agoHave they sorted out npm 5 yet? Bundling a borked version of npm with Node 8 was a real misstep I think.
- bertolo1988 9y agoahhahah
- jarvelov 9y agoMost of my issues were solved with 5.3.0 as of 8e979bf80. [0] >= 5.0 && < 5.3.0 were really messy and causing lots of problems for my dependencies with peer dependencies. And on top of that there were the issues with the lock file causing incomplete installs. Since 5.3.0 it's been reliable for me. I've stopped using yarn altogether after it just because it's yet another installation to manage. Although the build times are much better still with yarn, but npm is making some progress with every release. [0] https://github.com/npm/npm/commit/8e979bf80fb93233f19db003f08443e26cfc5e64 https://github.com/npm/npm/commit/8e979bf80fb93233f19db003f0...
- smt88 9y ago5.4 has major regressions and was a hellish nightmare for me for a while. I'm stuck on 5.3 now, too. I can't believe such a major tool is so poorly tested.
- Wintamute 9y agoI'm sticking with yarn for the time being I think. It feels years ahead of npm at the moment. Speed and robustness/correctness are much better, but stuff like `yarn upgrade-interactive` is also huge, also the workspaces feature.
- falafel 9y agoThey haven't unfortunately. npm 5.5.1 is still very broken, especially if you use postinstall scripts.
- ralmidani 9y agoMy current tools of choice for server-side are Python 3 + Django + Django REST Framework (DRF). I want to really get into Node, but developing with it currently feels like I'm Dr. Frankenstein hacking and stitching his monster together. I realize Node developers tend to prefer small, focused libraries rather than big, monolithic frameworks. But taken to an extreme, this results in a codebase that has litle beauty, consistency, or symmetry. Want to initialize an Express app? Don't use the new keyword. Want to declare a Mongoose schema? You have to use the new keyword. Express uses callbacks extensively, but for Mongoose I can configure promises (oh, should I also install and import Bluebird or just use global promises?) And really, why is body-parser installed separately from Express? I'm not disparaging Node in order to elevate Python, Django, and DRF. I really want to embrace Node and build fast, elegant, real-time, universal ES 2015+ Web apps. But as it stands now, exploring the Node ecosystem is exhausting and frustrating. Edit: if nobody builds a universal, consistent, ES 2015+ framework for Node, I fully intend to do it myself.
- kerryritter 9y agoI have the same complaints. I've found NestJS (https://nestjs.com https://nestjs.com) to be a wonderful solution for a lot of what you're talking about. There's a few recipes to get you up and rolling with a real framework and also an ORM (TypeORM or Mongoose). Highly recommend.
- deathtrader666 9y agoIf you want to build fast, elegant, real-time, consistent web apps for 2017 and onwards, take a look at Elixir and the Phoenix framework.