|
1
|
# Changelog
|
|
2
|
|
|
3
|
## v1.6.0
|
|
4
|
- Recommend absolute paths for rewrite targets. Contributed by @helfi92.
|
|
5
|
|
|
6
|
## v1.5.0
|
|
7
|
- Expose the HTTP request object in rewrite rules. Contributed by @VladShcherbin.
|
|
8
|
|
|
9
|
## v1.4.0
|
|
10
|
- The `.` (DOT) rule should only check the last path element. Contributed by @ntkme.
|
|
11
|
|
|
12
|
## v1.3.0
|
|
13
|
- Allow disabling of the `.` (DOT) rule via the `disableDotRule` option.
|
|
14
|
|
|
15
|
## v1.2.0
|
|
16
|
- Support definition of custom HTML `Accept` header values. Contributed by @cgmartin.
|
|
17
|
|
|
18
|
## v1.1.0
|
|
19
|
- Rewrite rules are now applied before the request URL is checked for dots.
|
|
20
|
- Rewrite rules can be defined as functions to have greater control over the `dot rule`.
|
|
21
|
|
|
22
|
## v1.0.0
|
|
23
|
This version introduces a fair amount of breaking changes. Specifically, instances of the historyApiFallback need to be created via the exported function. Previously, this was not necessary.
|
|
24
|
|
|
25
|
- **Breaking:** Support multiple instances of the historyApiFallback middleware with different configurations.
|
|
26
|
- **Breaking:** Loggers are configured per historyApiFallback middleware instance (see `README.md`).
|
|
27
|
- The fallback index HTML file can be configured. Default is `/index.html`.
|
|
28
|
- Additional rewrite rules can be defined via regular expressions.
|