Node.js pagination middleware and view helpers.
To be used in combination with database pagination plugins such as mongoose-paginate.
This module was created namely for use with Eskimo
npm install -S express-paginate
var paginate = require('express-paginate');
This creates a new instance of express-paginate
.
This middleware validates and supplies default values to req.query.limit
, req.query.page
, res.locals.paginate
, res.locals.hasPreviousPages
, and res.locals.hasNextPages
.
limit
a Number to limit results returned per page (defaults to10
)maxLimit
a Number to restrict the number of results returned to per page (defaults to50
) – through this, users will not be able to override this limit (e.g. they can't pass?limit=10000
and crash your server)
When you use the paginate
middleware, it injects a view helper function called paginate.href
as res.locals.paginate
, which you can use in your views for paginated hyperlinks (e.g. as the href
in <a>Prev</a>
or <a>Next</a>
).
By default, the view helper paginate.href
is already executed with the inherited req
variable, therefore it becomes a function capable of returning a String when executed.
When executed with req
, it will return a function with two optional arguments, prev
(Boolean) and params
(String).
The argument prev
is a Boolean and is completely optional (defaults to false
).
The argument params
is an Object and is completely optional.
Pass true
as the value for prev
when you want to create a <button>
or <a>
that points to the previous page (e.g. it would generate a URL such as the one in the href
attribute of <a href="/users?page=1&limit=10">Prev</a>
if req.query.page
is 2
).
Pass an object for the value of params
when you want to override querystring parameters – such as for filtering and sorting (e.g. it would generate a URL such as the one in the href
attribute of <a href="/users?page=1&limit=10&sort=name">Sort By Name</a>
if params
is equal to { sort: 'name' }
.
Note that if you pass only one argument with a type of Object, then it will generate a href
with the current page and use the first argument as the value for params
. This is useful if you only want to do something like change the filter or sort querystring param, but not increase or decrease the page number.
See the example below for an example of how implementation looks.
req
(required) – the request object returned from Express middleware invocation
prev
(optional) – a Boolean to determine whether or not to increment the hyperlink returned by1
(e.g. for "Next" page links)params
(optional) – an Object of querystring parameters that will override the current querystring inreq.query
(note that this will also override thepage
querystring value ifpage
is present as a key in theparams
object) (e.g. if you want to make a link that allows the user to change the current querystring to sort by name, you would haveparams
equal to{ sort: 'name' }
)
When you use the paginate
middleware, it injects a view helper Boolean called hasPreviousPages
as res.locals.hasPreviousPages
, which you can use in your views for generating pagination <a>
's or <button>
's – this utilizes req.query.page > 1
to determine the Boolean's resulting value (representing if the query has a previous page of results)
When you use the paginate
middleware, it injects a view helper function called hasNextPages
as res.locals.hasPreviousPages
, which you can use in your views for generating pagination <a>
's or <button>
's – if the function is executed, it returns a Boolean value (representing if the query has another page of results)
By default, the view helper paginate.hasNextPages
is already executed with the inherited req
variable, therefore it becomes a function capable of returning a Boolean when executed.
When executed with req
, it will return a function that accepts two required arguments called pageCount
and resultsCount
.
req
(required) – the request object returned from Express middleware invocation
pageCount
(required) – a Number representing the total number of pages for the given query executed on the page
// # app.js
var express = require('express');
var paginate = require('express-paginate');
var app = express();
// keep this before all routes that will use pagination
app.use(paginate.middleware(10, 50));
app.get('/users', function(req, res, next) {
// This example assumes you've previously defined `Users`
// as `var Users = db.model('Users')` if you are using `mongoose`
// and that you've added the Mongoose plugin `mongoose-paginate`
// to the Users model via `User.plugin(require('mongoose-paginate'))`
Users.paginate({}, req.query.page, req.query.limit, function(err, pageCount, users, itemCount) {
if (err) return next(err);
res.format({
html: function() {
res.render('users', {
users: users,
pageCount: pageCount,
itemCount: itemCount
});
},
json: function() {
// inspired by Stripe's API response for list objects
res.json({
object: 'list',
has_more: paginate.hasNextPages(req)(pageCount),
data: users
});
}
});
});
});
app.listen(3000);
//- users.jade
h1 Users
//- this will simply generate a link to sort by name
//- note how we only have to pass the querystring param
//- that we want to modify here, not the entire querystring
a(href=paginate.href({ sort: 'name' })) Sort by name
//- this assumes you have `?age=1` or `?age=-1` in the querystring
//- so this will basically negate the value and give you
//- the opposite sorting order (desc with -1 or asc with 1)
a(href=paginate.href({ sort: req.query.age === '1' ? -1 : 1 })) Sort by age
ul
each user in users
li= user.email
include _paginate
//- _paginate.jade
//- This examples makes use of Bootstrap 3.x pagination classes
if paginate.hasPreviousPages || paginate.hasNextPages(pageCount)
.navigation.well-sm#pagination
ul.pager
if paginate.hasPreviousPages
li.previous
a(href=paginate.href(true)).prev
i.fa.fa-arrow-circle-left
| Previous
if paginate.hasNextPages(pageCount)
li.next
a(href=paginate.href()).next
| Next
i.fa.fa-arrow-circle-right