MORPH
SIGN IN SIGN UP
morphadmin / express-bench

Fast, unopinionated, minimalist web framework for node.

0 0 10 JavaScript
Normal View History Raw
docs: add license comments
2015-06-18 23:00:20 -04:00
/*!
* express
* Copyright(c) 2009-2013 TJ Holowaychuk
* Copyright(c) 2013 Roman Shtylman
* Copyright(c) 2014-2015 Douglas Christopher Wilson
* MIT Licensed
*/
perf: enable strict mode
2015-06-18 23:01:18 -04:00
'use strict';
prepping for connect 1.0
2011-03-01 10:54:04 -08:00
/**
* Module dependencies.
*/
Add express.json and express.urlencoded to parse bodies closes #2211
2017-09-28 13:22:36 -04:00
var bodyParser = require('body-parser')
fix(refactor): prefix built-in node module imports 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
2024-12-21 22:58:33 +01:00
var EventEmitter = require('node:events').EventEmitter;
Fix internal utils.merge deprecation warnings
2014-10-22 15:18:10 -04:00
var mixin = require('merge-descriptors');
some code cleanup
2014-03-25 15:23:04 -07:00
var proto = require('./application');
Use router module for routing closes #2411
2015-07-06 23:46:00 -04:00
var Router = require('router');
some code cleanup
2014-03-25 15:23:04 -07:00
var req = require('./request');
var res = require('./response');
setting up proto
2011-10-07 09:23:54 -07:00
uncommented old code
2011-10-07 10:01:30 -07:00
/**
* Expose `createApplication()`.
*/
exports = module.exports = createApplication;
/**
* Create an express application.
*
* @return {Function}
* @api public
*/
function createApplication() {
remove app.router and refactor middleware processing This is an overhaul of middleware processing, Router and Route. Connect is no longer used to process the middleware stack. This functionality has been split into two parts: middleware stack and default error response. The entry point for request processing is the `app.handle` method. It sets up the default error response handle (to run in the event of no other error handler) and then triggers the app router (instance of Router) to handle the request. The app router `handle` function contains the middleware dispatch layer previously in the connect codebase. This layer handle the logic for dispatching `.use` calls (stripping paths if needed). The app contains a base router `app._router`. New routes can be created and `.use`d on this router to organize routes into files. Routers now have the following methods `.use`, `.all`, `.param` which are all public. Additionally, Routers have a `.route(path)` method which returns a new instance of Route for the requested path. Route(s) are isolated middleware stacks and contain methods for the HTTP verbs as well as an `.all` method to act similar to middleware. These methods are chainable to easily describe requirements for a route. var route = Router.route('/foo'); // or 'app.route('/foo')' route .all(auth) .get(function(...) {}) .all(more_checks) .post(function(...) {}) Any Route and Router methods which accept handlers also accept error (arity 4) handlers which will also behave as expected. Finally, the `app.router` getter has been removed. Middleware and handlers are run IN THE ORDER they are seen in the file. This means that code which injected the `app.router` and then added error handlers (or other middleware) will need to be updated to move those handlers after any requests added on the app object. The examples have been updated accordingly. This is the largest breaking change to codebases in this commit.
2014-01-25 17:57:25 -05:00
var app = function(req, res, next) {
app.handle(req, res, next);
};
Fix constructing application with non-configurable prototype properties fixes #2561
2015-03-01 16:33:09 -05:00
mixin(app, EventEmitter.prototype, false);
mixin(app, proto, false);
remove app.router and refactor middleware processing This is an overhaul of middleware processing, Router and Route. Connect is no longer used to process the middleware stack. This functionality has been split into two parts: middleware stack and default error response. The entry point for request processing is the `app.handle` method. It sets up the default error response handle (to run in the event of no other error handler) and then triggers the app router (instance of Router) to handle the request. The app router `handle` function contains the middleware dispatch layer previously in the connect codebase. This layer handle the logic for dispatching `.use` calls (stripping paths if needed). The app contains a base router `app._router`. New routes can be created and `.use`d on this router to organize routes into files. Routers now have the following methods `.use`, `.all`, `.param` which are all public. Additionally, Routers have a `.route(path)` method which returns a new instance of Route for the requested path. Route(s) are isolated middleware stacks and contain methods for the HTTP verbs as well as an `.all` method to act similar to middleware. These methods are chainable to easily describe requirements for a route. var route = Router.route('/foo'); // or 'app.route('/foo')' route .all(auth) .get(function(...) {}) .all(more_checks) .post(function(...) {}) Any Route and Router methods which accept handlers also accept error (arity 4) handlers which will also behave as expected. Finally, the `app.router` getter has been removed. Middleware and handlers are run IN THE ORDER they are seen in the file. This means that code which injected the `app.router` and then added error handlers (or other middleware) will need to be updated to move those handlers after any requests added on the app object. The examples have been updated accordingly. This is the largest breaking change to codebases in this commit.
2014-01-25 17:57:25 -05:00
Use Object.create to setup request & response prototypes
2017-02-23 01:52:49 -05:00
// expose the prototype that will get set on requests
app.request = Object.create(req, {
app: { configurable: true, enumerable: true, writable: true, value: app }
})
// expose the prototype that will get set on responses
app.response = Object.create(res, {
app: { configurable: true, enumerable: true, writable: true, value: app }
})
using connect.proto.use
2011-10-07 09:29:36 -07:00
app.init();
setting up proto
2011-10-07 09:23:54 -07:00
return app;
}
expose prototype
2011-10-07 13:13:32 -07:00
/**
Added exports.{request,response}
2011-11-28 11:48:27 -08:00
* Expose the prototypes.
expose prototype
2011-10-07 13:13:32 -07:00
*/
exports.application = proto;
Added exports.{request,response}
2011-11-28 11:48:27 -08:00
exports.request = req;
exports.response = res;
expose prototype
2011-10-07 13:13:32 -07:00
uncommented old code
2011-10-07 10:01:30 -07:00
/**
* Expose constructors.
*/
Use router module for routing closes #2411
2015-07-06 23:46:00 -04:00
exports.Route = Router.Route;
expose router
2011-12-06 16:36:52 -08:00
exports.Router = Router;
uncommented old code
2011-10-07 10:01:30 -07:00
remove last pieces of connect dependency - copy over patch.js to shim ServerResponse - bundle `static` middleware
2014-02-15 20:20:12 -05:00
/**
* Expose middleware
*/
errorHandler title
2011-03-30 21:59:15 -07:00
Add express.json and express.urlencoded to parse bodies closes #2211
2017-09-28 13:22:36 -04:00
exports.json = bodyParser.json
Add express.raw to parse bodies into Buffer closes #3708
2018-08-08 07:42:00 +03:00
exports.raw = bodyParser.raw
use serve-static for static middleware
2014-03-05 21:58:49 -08:00
exports.static = require('serve-static');
Add express.text to parse bodies into string closes #3455
2017-10-23 18:00:19 +03:00
exports.text = bodyParser.text
Add express.json and express.urlencoded to parse bodies closes #2211
2017-09-28 13:22:36 -04:00
exports.urlencoded = bodyParser.urlencoded
Reference in New Issue Copy Permalink