1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
next.js/server/lib/path-match.js
Arunoda Susiripala abe6e3ea47 Use a latest version of path-to-regexp for path-match (#3655)
* Use the latest path-to-regexp for path-match.

* Fix the error route resolving.

* Give proper credit to path-match

* Remove an unwanted route.

* Revert "Remove an unwanted route."

This reverts commit 523c1687da8ddd499819e70df81567ec208e5998.

* Add a comment why we need to keep _error.js route.
2018-02-01 19:54:09 +01:00

42 lines
1.1 KiB
JavaScript

// We borrow this code from https://github.com/pillarjs/path-match
// That's because, ^^^ package comes with very old version of path-to-regexp
// So, it'll give us issues when the app has used a newer version of path-to-regexp
// (When webpack resolving packages)
var pathToRegexp = require('path-to-regexp')
var createError = require('http-errors')
module.exports = function (options) {
options = options || {}
return function (path) {
var keys = []
var re = pathToRegexp(path, keys, options)
return function (pathname, params) {
var m = re.exec(pathname)
if (!m) return false
params = params || {}
var key, param
for (var i = 0; i < keys.length; i++) {
key = keys[i]
param = m[i + 1]
if (!param) continue
params[key.name] = decodeParam(param)
if (key.repeat) params[key.name] = params[key.name].split(key.delimiter)
}
return params
}
}
}
function decodeParam (param) {
try {
return decodeURIComponent(param)
} catch (_) {
throw createError(400, 'failed to decode param "' + param + '"')
}
}