Morph MORPH
SIGN IN SIGN UP
morphadmin / user-project
0 0 98 JavaScript
Normal View History Raw
examples: use strict mode
2022-02-02 01:30:51 -05:00
'use strict'
Added exception example
2010-07-13 08:48:44 -07:00
/**
* Module dependencies.
*/
clean up code consistency
2014-03-27 09:15:27 -07:00
var express = require('../../');
var logger = require('morgan');
var app = module.exports = express();
lint: remove usages of "==" closes #3540
2018-01-21 20:14:47 -05:00
var test = app.get('env') === 'test'
Added exception example
2010-07-13 08:48:44 -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
if (!test) app.use(logger('dev'));
fixed error example
2011-11-20 12:03:45 -08:00
// error handling middleware have an arity of 4
// instead of the typical (req, res, next),
// otherwise they behave exactly like regular
// middleware, you may have several of them,
// in different orders etc.
function error(err, req, res, next) {
// log it
clean up error example
2012-04-26 04:56:23 -07:00
if (!test) console.error(err.stack);
fixed error example
2011-11-20 12:03:45 -08:00
// respond with 500 "Internal Server Error".
docs: update examples for deprecations
2014-08-06 18:13:54 -04:00
res.status(500);
res.send('Internal Server Error');
fixed error example
2011-11-20 12:03:45 -08:00
}
Added exception example
2010-07-13 08:48:44 -07:00
lint: remove unused parameters in examples closes #5113
2023-02-03 20:34:39 +05:30
app.get('/', function () {
misc
2010-11-25 13:41:50 -08:00
// Caught and passed down to the errorHandler middleware
throw new Error('something broke!');
Added exception example
2010-07-13 08:48:44 -07:00
});
Updated examples
2010-07-26 13:36:21 -07:00
app.get('/next', function(req, res, next){
misc
2010-11-25 13:41:50 -08:00
// We can also pass exceptions to next()
examples: comment the usage of process.nextTick closes #2903 closes #2908
2016-02-25 07:46:14 +05:00
// The reason for process.nextTick() is to show that
// next() can be called inside an async operation,
// in real life it can be a DB read or HTTP request.
fixed error example
2011-11-20 12:03:45 -08:00
process.nextTick(function(){
next(new Error('oh no!'));
});
Added exception example
2010-07-13 08:48:44 -07:00
});
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
// the error handler is placed after routes
// if it were above it would not receive errors
// from app.get() etc
app.use(error);
tests: exclude untestable lines in examples from coverage
2014-05-28 00:07:27 -04:00
/* istanbul ignore next */
Updated error example with acceptance tests.
2011-12-18 17:27:13 +01:00
if (!module.parent) {
app.listen(3000);
console.log('Express started on port 3000');
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
}
Reference in New Issue Copy Permalink