As maintainers of the open source framework Electron, we try to be diligent about the work we take on. Apps like Visual Studio Code, Slack, Notion, or 1Password are built on top of Electron and make use of our unique mix of native code and web technologies to make their users happy. That requires focus: There’s always more work to be done than we have time and resources for. In practice, that means that we don’t want to spend time thinking about the server infrastructure for the project — and we’re grateful for the support we receive from Heroku, where we can host load-intensive apps without worrying about managing the underlying infrastructure. In this blog post, we’ll take a look at...

Intro

The Heroku Node.js buildpack now supports pnpm, an alternative dependency manager. Early Node.js application owners who've taken advantage of pnpm support have seen 10-40% faster install times compared to NPM on Heroku deployments. It’s an excellent choice for managing packages in the Node.js ecosystem because it:

• Minimizes disk space with its content-addressable package store.
• Speeds up installation by weaving together the resolve, fetch, and linking stages of dependency installation.

This post will introduce you to some of the benefits of the pnpm package manager and walk you through creating and deploying a sample application.

Yarn is a JavaScript package manager that also gives developers a project management toolset and a zero-install deployment solution. Heroku supports Yarn 2, 3, and 4, so developers are able to take advantage of zero-installs during their Node.js builds. We’ll go over a popular use case for Yarn that was enhanced by Yarn 2 and later releases: using workspaces to manage dependencies for a monolithic repository, also known as a multi-package repository or a monorepo.

Our Yarn Workspaces tutorial will cover Yarn monorepo setup and how to take advantage of Yarn’s cache to manage monorepo dependencies. Prerequisites for this include a development environment with Node installed. To follow...

There are always challenges when it comes to debugging applications. Node.js' asynchronous workflows add an extra layer of complexity to this arduous process. Although there have been some updates made to the V8 engine in order to easily access asynchronous stack traces, most of the time, we just get errors on the main thread of our applications, which makes debugging a little bit difficult. As well, when our Node.js applications crash, we usually need to rely on some complicated CLI tooling to analyze the core dumps.

The recent introduction of Platform Events and Change Data Capture (CDC) in Salesforce has launched us into a new age of integration capabilities. Today, it's possible to develop custom apps that respond to activity in Salesforce. Whether you're creating a memorable customer interaction or implementing an internal workflow for employees, consider an event-sourced design to improve responsiveness and durability of the app.

In this article, we'll look at an event-sourced app architecture that consumes the Salesforce Streaming API using the elegant jsforce JavaScript library in a Node app on Heroku.

Streaming with jsforce

In summer 2018, the open-source jsforce library...