routr - npm Package Versions

3.0.1

• [#114] fix handling of array like query params

3.0.0

Breaking Changes

• [#110] routr uses native URLSearchParams instead of query-string to parse query strings. As a consequence, parsing ?foo will result in { foo: '' } as specified in the WHATWG spec instead of { foo: null } as query-string would do. Also, URLSearchParams is not available in older browsers (noticeably IE11). If you need to support them, you can either add a URLSearchParams polyfill or inject query-string when instantiating routr:

router = new Routr(routes, {
    queryLib: require('query-string'),
});

• [#113] Updated path-to-regexp to its latest version

2.1.0

• [#37] Enhance makePath for routes with path array

2.0.2

• [#36] Bug fix: Add support for question marks in hash fragments

2.0.1

• [#35] Fix decodeURIComponent of undefined bug