Js

Node Streams Part 1: Readable Streams

7 minute read Published:

A deep dive into readable streams
Whether you know it or not, if you have coded anything in Node.js it is likely that you have used streams. An express server serves streams as its responses and accepts streams as the requests. You can think of a stream as a path for chunked data to travel down. Data is buffered and sent along in chunks, like trucks down a highway. In this way you can send a large amount of data in a manageable way to different processes without sacrificing performance.

Node Streams: an overview

3 minute read Published:

What is a stream? Why would you use one?
Whether you know it or not, if you have coded anything in Node.js it is likely that you have used streams. An express server serves streams as responses and accepts streams as requests. You can think of a stream as a path for chunked data to travel down. Data is buffered and sent along in chunks, like trucks down a highway. In this way you can send a large amount of data in a manageable way to different processes without sacrificing performance.

Concurrent command line processes

1 minute read Published:

An easy way to combine tasks
I recently had a project in which I wanted to use both webpack and gulp without the hassle of opening multiple console windows. After a little bit of searching I found the package Concurrently which just feels good to use: npm run dev And you’re done. To get it set up open up your package.json and put in some scripts you’d like to use like this: { scripts: { serve: webpack-dev-server --inline --hot --watch --config=webpack.