Used to get all registered routes in Express Application
Special-cased "all" method, applying the given route path,
middleware, and callback to every HTTP method.
The app.routes object houses all of the routes defined mapped by the associated HTTP verb. This object may be used for introspection capabilities, for example Express uses this internally not only for routing but to provide default OPTIONS behaviour unless app.options() is used. Your application or framework may also remove routes by simply by removing them from this object.
Stack of configured routes
Configure callback for zero or more envs,
when no env is specified that callback will
be invoked for all environments. Any combination
can be used multiple times, in any order desired.
Examples:
app.configure(function(){ // executed for all envs });
app.configure('stage', function(){ // executed staging env });
app.configure('stage', 'production', function(){ // executed for stage and production });
Note:
These callbacks are invoked immediately, and are effectively sugar for the following:
var env = process.env.NODE_ENV || 'development';
switch (env) {
case 'development':
...
break;
case 'stage':
...
break;
case 'production':
...
break;
}
Initialize application configuration.
Disable setting.
Check if setting is disabled.
app.disabled('foo') // => true
app.enable('foo') app.disabled('foo') // => false
Enable setting.
Check if setting is enabled (truthy).
app.enabled('foo') // => false
app.enable('foo') app.enabled('foo') // => true
Register the given template engine callback fn
as ext.
By default will require() the engine based on the
file extension. For example if you try to render
a "foo.jade" file Express will invoke the following internally:
app.engine('jade', require('jade').__express);
For engines that do not provide .__express out of the box,
or if you wish to "map" a different extension to the template engine
you may use this method. For example mapping the EJS template engine to
".html" files:
app.engine('html', require('ejs').renderFile);
In this case EJS provides a .renderFile() method with
the same signature that Express expects: (path, options, callback),
though note that it aliases this method as ejs.__express internally
so if you're using ".ejs" extensions you dont need to do anything.
Some template engines do not follow this convention, the Consolidate.js library was created to map all of node's popular template engines to follow this convention, thus allowing them to work seamlessly within Express.
Initialize the server.
Listen for connections.
A node http.Server is returned, with this
application (which is a Function) as its
callback. If you wish to create both an HTTP
and HTTPS server you may do so with the "http"
and "https" modules as shown here:
var http = require('http') , https = require('https') , express = require('express') , app = express();
http.createServer(app).listen(80); https.createServer({ ... }, app).listen(443);
Return the app's absolute pathname based on the parent(s) that have mounted it.
For example if the application was mounted as "/admin", which itself was mounted as "/blog" then the return value would be "/blog/admin".
Render the given view name name with options
and a callback accepting an error and the
rendered template string.
Example:
app.render('email', { name: 'Tobi' }, function(err, html){ // ... })
or fn
Assign setting to val, or return setting's value.
app.set('foo', 'bar'); app.get('foo'); // => "bar" app.set('foo', ['bar', 'baz']); app.get('foo'); // => ["bar", "baz"]
Mounted servers inherit their parent server's settings.
Generated using TypeDoc
Express instance itself is a request handler, which could be invoked without third argument.