mirror of
https://github.com/zebrajr/express.git
synced 2025-12-06 00:19:48 +01:00
Since v5 relies on node >= 18, this is now possible (since v16, v14.18.0 [^1][^2]). It's functionally irrelevant: 1. It's not required for CJS nor ESM (with a few exceptions [^3]) 2. It has no performance promises However, there are upsides to this approach: 1. It brings clear boundaries to what's a built-in and what's an external dependency 2. It reduces the risk of importing unwanted deps where a built-in is expected 3. It's slightly more interoperable with other JS runtimes that provide node compatibility[^4], albeit only during development. Once imported from npm, built-ins are assumed. [^1]:https://nodejs.org/docs/latest-v22.x/api/modules.html#built-in-modules [^2]:https://github.com/nodejs/node/pull/37246 [^3]:https://nodejs.org/api/modules.html#built-in-modules-with-mandatory-node-prefix [^4]:https://docs.deno.com/runtime/fundamentals/node/#using-node's-built-in-modules
43 lines
1.0 KiB
JavaScript
43 lines
1.0 KiB
JavaScript
'use strict'
|
|
|
|
var assert = require('node:assert')
|
|
var express = require('../');
|
|
var request = require('supertest');
|
|
|
|
describe('middleware', function(){
|
|
describe('.next()', function(){
|
|
it('should behave like connect', function(done){
|
|
var app = express()
|
|
, calls = [];
|
|
|
|
app.use(function(req, res, next){
|
|
calls.push('one');
|
|
next();
|
|
});
|
|
|
|
app.use(function(req, res, next){
|
|
calls.push('two');
|
|
next();
|
|
});
|
|
|
|
app.use(function(req, res){
|
|
var buf = '';
|
|
res.setHeader('Content-Type', 'application/json');
|
|
req.setEncoding('utf8');
|
|
req.on('data', function(chunk){ buf += chunk });
|
|
req.on('end', function(){
|
|
res.end(buf);
|
|
});
|
|
});
|
|
|
|
request(app)
|
|
.get('/')
|
|
.set('Content-Type', 'application/json')
|
|
.send('{"foo":"bar"}')
|
|
.expect('Content-Type', 'application/json')
|
|
.expect(function () { assert.deepEqual(calls, ['one', 'two']) })
|
|
.expect(200, '{"foo":"bar"}', done)
|
|
})
|
|
})
|
|
})
|