Express middleware design patterns are being used more and more widely in frontend development. Drawing on real projects, this article digs into their core principles and best practices.
Basic Usage
Here is a complete example:
const fs = require('fs')
const { Transform, pipeline } = require('stream')
const { promisify } = require('util')
const pipelineAsync = promisify(pipeline)
const csvToJson = new Transform({
transform(chunk, encoding, callback) {
const lines = chunk.toString().split('\n')
const headers = lines[0].split(',')
for (let i = 1; i < lines.length; i++) {
if (!lines[i].trim()) continue
const values = lines[i].split(',')
const obj = {}
headers.forEach((h, idx) => obj[h.trim()] = values[idx]?.trim())
this.push(JSON.stringify(obj) + '\n')
}
callback()
}
})
Mind the edge-case handling—that's critical in production.
Advanced Usage
The key is to understand the core logic:
const express = require('express')
const app = express()
app.use(express.json())
class AppError extends Error {
constructor(status, message) {
super(message); this.statusCode = status
}
}
const asyncHandler = (fn) => (req, res, next) =>
Promise.resolve(fn(req, res, next)).catch(next)
app.get('/api/users/:id', asyncHandler(async (req, res) => {
const user = await User.findById(req.params.id)
if (!user) throw new AppError(404, '用户不存在')
res.json({ data: user })
}))
Performance tuning should fit the specific scenario—you don't need to over-optimize every case.
Practical Cases
Here are a few ways we can improve on this:
const fs = require('fs')
const { Transform, pipeline } = require('stream')
const { promisify } = require('util')
const pipelineAsync = promisify(pipeline)
const csvToJson = new Transform({
transform(chunk, encoding, callback) {
const lines = chunk.toString().split('\n')
const headers = lines[0].split(',')
for (let i = 1; i < lines.length; i++) {
if (!lines[i].trim()) continue
const values = lines[i].split(',')
const obj = {}
headers.forEach((h, idx) => obj[h.trim()] = values[idx]?.trim())
this.push(JSON.stringify(obj) + '\n')
}
callback()
}
})
This approach has been running stably in production for over half a year, so it's battle-tested.
Performance Optimization
Let's start with the basic implementation:
const express = require('express')
const app = express()
app.use(express.json())
class AppError extends Error {
constructor(status, message) {
super(message); this.statusCode = status
}
}
const asyncHandler = (fn) => (req, res, next) =>
Promise.resolve(fn(req, res, next)).catch(next)
app.get('/api/users/:id', asyncHandler(async (req, res) => {
const user = await User.findById(req.params.id)
if (!user) throw new AppError(404, '用户不存在')
res.json({ data: user })
}))
This snippet shows the basic usage. In a real project, you'll also need to handle errors and edge cases.
Common Traps
Building on that, we can optimize further:
const fs = require('fs')
const { Transform, pipeline } = require('stream')
const { promisify } = require('util')
const pipelineAsync = promisify(pipeline)
const csvToJson = new Transform({
transform(chunk, encoding, callback) {
const lines = chunk.toString().split('\n')
const headers = lines[0].split(',')
for (let i = 1; i < lines.length; i++) {
if (!lines[i].trim()) continue
const values = lines[i].split(',')
const obj = {}
headers.forEach((h, idx) => obj[h.trim()] = values[idx]?.trim())
this.push(JSON.stringify(obj) + '\n')
}
callback()
}
})
This pattern is especially handy in large projects, and it noticeably cuts maintenance cost.
Summary
- The code examples are for reference only—adapt them to your own use case.
- Express middleware design patterns aren't a silver bullet—choose them based on your project's scale and tech stack.
- Understanding the underlying principles matters more than memorizing the API.
