Node.js

“We switched over from Apollo on node to async-graphql on Rust.”

“I transpile for prod, but use --strip-types when running in dev”

“we've been raw dogging MySQL and node.js at work for over a year”

“Also we use node which it Little horse doesn't seem to support.”

“Practically all the CPU time ends up spent in your nodejs application server.”

“a basic, scroll-bug-free, 650 LOC node.js app that basically circumvents this issue completely”

“We instrument Python, Node/TS, and Java to record deep context into a circular buffer.”

“We do use workers, but with hono so it's easy to deploy it on render with node.”

“It was a simple Node.js + PostgreSQL server running on a fire-walled on-premise machine. We let it run untouched for just over two years.”

“I have this setup and integrated for Node/Bun”

“we moved off of wkhtmltopdf to a nodejs service which received static html and rendered it to pdf”

“Back to Node we go.”

“We use Testcontainers (https://testcontainers.com/) in our node.js / vitest / kysely stack.”

“We generally try to stay in line with the supported versions of the technologies we use: Postgres, NodeJS, Redis, etc.”

“we use a node library that speaks the HTML Canvas API and can generate PDFs.”

“I've also done similar systems in other languages, especially Node.js, Python, and Rust, but they haven't been as productive”

“migrate a large node repository to ESM”

“We run Next.js on our own server as we use node-specific APIs in various backend-y places of Next”

“this is my experience coming from Java, Node, and Python”

“It only took me a couple of months to realized what Ruby on Rails offers & the vibrant ecosystem it has.”

“Musl causes a more regular pain of node add-ons needing to be specially compiled”

“JavaScript (both Node and browser, sometimes React), I'm the only one on the team”

“It's always a bit odd coming from npm/node into something like Deno”

“I'm a big ts and nodejs user”

“we moved to Nuxt server side rendered on Node (Heroku)”

“My chosen stack is React (DaisyUI, deployed with cloudflare) + Node”

“I started a large Node project that a teammate moved to TS”

“To learn more about Node.js, I decided to build the website for the screencast myself, rather than using something like WordPress.”

“a set of services which were written in Java and NodeJS”

“We switched our main service, which is a nodejs monolith, and did not get any cost improvement”

“eventually learned to just use the tools I knew (react, node, postgres)”

“Our stack is (per country) 3 nodejs services, PostgreSQL, redis and some frontend services.”

“When I did my last startup we switched from a Python API to Node for this reason.”

“I once had to fix something in prod during a demo... manually change a line in a bundled and minimised Nodejs app!”

“here is one of our service files for systemd to manage a Node.js backend instance”

“we migrated all erlang, golang and nodejs code to edge workers on cloudflare and simply did not need to run containers anymore”

“I get to run two versions of node on one Linux and pretend I didn't just sweep all these serious issues”

“having built on things like Python+FastAPI, Node+Express/Hapi/Apollo, and Rust+Actix”

“After that, I wrote something with a Typescript/Node backend. IDK if it was better or worse than .NET.”

“we switched our nodejs workload to graviton (c6g from c5)”

“We have a mixture of python, java, go, protobuf, and node.”

“our apps are for the most part platform agnostic apps on Node.”

“We have quite a few Lambda functions (written in Node) that I believe pre-date even my tenure at the company”

“having worked with Node for almost 10 years now, with a number of bundlers, most in Javascript but some in other languages”

“At my workplace, we have a node.js service that solves Vehicle Routing Problems”

“we switched to using native SQLite via a bridge to a Node process”

“We went there from node and we did try a lot of other backend stacks”

“We switched from Node.js to Go in the beginning of 2020”

“Fullstack Angular + Node -> Backend Node with shift to TypeScript near the end”

“we also worked with python, nodejs, some Go.”

“other languages and frameworks I've used in prod (Golang, Dotnet, Dotnet Core, Node, Ts-Node, Rails, PHP, etc)”

“In fact, I contributed to a Node.js framework for implementing CQRS and Event Sourcing.”

“The solution we used was to make our UI in HTML/JS/Angular and have it talk to a Lisp backend with Node.js.”

“this setup might be lot easier to deal with than Appollo and node.js”

“I've been hacking a small Node app in my dev environment for the past few weeks.”

“a couple of nodejs apps”

“a.o nginx and nodejs have no recent versions available; versions that we either need for features”

“Our product is actually comprised of multiple NodeJS servers that are spawned as child processes in one master Node procees”

“Having spent the last several years using TS on Node in production”

“some other tasks needed to use node and puppeter(a Chrome) wrapper - it was crashing a lot”

“The services that actually display stuff on the screen (Node.js) run as their own container with their own processes”

“Groupon still used it even after they ditched Ruby for node.js”

“it seemed to be a combination of Node + Consul DNS”

“I've been using TiddlyWiki in the node.js-based server mode.”

“Go or Node (both of which I have used in production in the last month, and wouldn't take over Scala”

“which we use in our NodeJS codebase.”

“running Node code on each violation to filter and format the violation JSON”

“we migrated from NodeJS / Angular to Haskell / Elm and couldn't be happier.”

“We did the same with our open source project. We ditched Clojure and Clojurescript for NodeJS and JavaScript”

“We switched over from our old NodeJS backend to a new Go backend recently”

“For Node we use node-fetch which mimics the fetch API using the native HTTP module in the background”

“We've written our own blue-green deployment scripts for Spring Boot, Node.js/React/Vue, and Python.”

“I haven't had a single performance issue with a bunch of different Rails, Flask, Node, Phoenix and Jekyll apps”

“Most of the codebase is in Ruby/Rails and NodeJS.”

“I've been using this exact structure too, via Nuxt: Node/Express + Vue on the front end”

“Matter is a web app, written in NodeJS.”

“I used to manually compile things like Node.js and ripgrep from source to get up-to-date versions”

“Yeah, we use tsc for node.”

“At the moment we are using the Node.js runtime with Typescript.”

“In our case we are using Node.JS and all SQL libraries are very very slow.”

“We've used the Node.js containers in production and investigated the other languages, but never deployed them.”

“we run the nodejs version using nodemon so that it reloads whenever the webpack watch mode rebuilds”

“most of which use Golang, some Python and Node and Java.”

“Just checked memory use on some services we run on Go, Node, and Java.”

“somehow at Node 9.0 it's still needed.”

“We've got two nodejs implementations of the pinning service API you can self-deploy, and then we run a Hashbase instance at hashbase.io”

“more recently implemented in Node.js.”

“some of these run in Linux, php, nodes, python and so on.”

“I'm writing Node Lambda's.”

“I've actually been using this to take a break from Node and start learning Django.”

“Generated contracts are isomorphic and work well from Node.js and a browser while being simply packed with NPM.”

“We run an entirely node stack so Lerna enables this in the first place.”

“I'm 100% node/react/etc”

“All our web projects are node, typescript, and the front end stuff the client wants us to use (though we default to angular).”

“I could have done that in Node (we did for a long time), but I decided that with the latest set of changes we'd bring this component in line”

“I've been happily using it since generators were available under a flag with node 0.11”

“We switched a large Nodejs project from TFS to GitLab and it's been night-and-day on our productivity.”

“breaking apart the app into micro services which are a combination of node js, golang, and Python/flask apps”

“pipe updates to a java/node app which then would write updates via the web socket interface”

“to measure the performance gains from multiple Node workers and the linked-list messaging queue”

“I'd rather not use a non-LTS version in production since I don't want to have to keep track of changes.”

“I'm eagerly awaiting native async/await in NodeJS (scheduled for version 8 AFAIK).”

“our node.js adapter uses leveldown, so any *down backend can be plugged in.”

“I proxy with nginx for IP rate limiting and node.js for failed password attempts rate limiting.”

“When we switched to Clojure (from nodejs)”

“we started with Rails, displacing a Node.js implementation that was poorly designed and messily implemented”

“We initially had a small Node.js server, just to experiment with, but I discovered that it had no error handling at all.”

“We've run through PHP, Rails, Node, Python (Django) and lately Go.”

“We've run through PHP, Rails, Node, Python (Django) and lately Go.”

“We run a good-sized app API using Typescript with Node.js.”

“Then we run Python (with virtualenv or Buildout) or Node (with npm)”

“It helped that the storage and query approach had good impedance match with NodeJS.”

“instead of extending some existing node.js modules that existed in the community”

“experiencing Django and Node was an eye opener.”

“I've been using Heroku for a Node apps and was sad that deploying Go apps required a custom buildpack.”

“I've been using Visual Studio 2013 + Node Tools + Web Essentials to do all my Web and Node.js projects.”

“devs install Node deps on the staging server, forget to tell ops, service crashes when deployed in prod”

“Ruby, PHP, NodeJS, Apache...it's all there.”

“I have been using it for Node.js development for the past few months”

“we run it on node and setup a simple API that mirrors the vendor's API”

“node.js doesn't have v1.0 release yet, but I still use it... using an unblessed release in production is acceptable.”

“deploy, replacing a Node.js rig.. for no reason other than we want Lua everywhere and no more javascript”

“Open sourcing more of the node.js code/systems I have written in the past year”

“All those different templates get written into just one XSL file automatically with the help of node.js' gulp.”

“I've been using node.js & some Sinatra lately.”

“We use a variety of other technologies in our stack (Node, Backbone, etc.)”

“Currently, we use Node and may be doing long-term embedded installs of it”

“I used this (dokku on DigitalOcean as described) in production for several months for NodeJS”

“I've worked on everything from Spring projects to NodeJS projects”

“wrote a Shoutcast replacement in Node.js that the station has been running in production for the past 18 months”

“For the latest project at work I've been using Yeoman with Grunt, Bower and NPM for the Node part.”

“I have several Node applications in production at my company.”

“which I'm currently using in production for the startup I work for”

“I've been experimenting with node.js for a side project and its pretty easy to setup a project entirely in CS.”

“we use node.js heavily, and I would like create npm modules”

“One is for node.js and uses node's Buffer methods to do the fast byte to number conversions.”

“We use a very similar set up in a large Node.js app I'm working on.”

“I'm dabbling in Python and Node.js to see if I might want to move more of the backend services away from PHP”

“For Javascript or HTML/CSS related courses we use either Node.js with jsdom or Node.js with phantomjs”

“It's composed of many small applications, each deployed as a WAR file since the non-Node.js part of the site is on the JVM.”

“Bundler: Our node.exe based - for all compilation and minifiying of less, css, js assets.”

“We've been running node.js since the 0.2 days and we've solved interesting scaling problems.”

“we run a pretty serious production Node.js app.”

“There isn't really any clean, low-level websocket implementations for node that worked anymore”

“especially in Node.js where watch->multi->exec callback stacks can be interrupted by other events”

“I'm glad they're happy with the rewrite, but honestly, this makes me feel a bit nervous about updating my Node app”

“We've migrated some key parts out to HTTP services written in Scala, Java, or node.js.”

“Hosted on nodeJS hiding behind nginx.”

“I had to compile v8 and node to link against and scons wasn't playing nice w/ the build environment.”

“They're built for lucid, but run fine on maverick, and like everything else in that PPA, are used in production”