54e45eb74d
This PR adds the `_error`-page as an `404.html`-export, even when it is not explicitly defined in a custom `exportPathMap`. It also fixes two false negative tests related to this. Previously the tests were matching the fallback 404-page from the test-server, rather than the `404.html`-page from next, which was actually not being generated. The test server is also not set up to serve `/404.html` as `/404` which the tests now reflect. **Caveat** In its current state, this PR removes `/404.html` from the `defaultPathMap` passed to the custom `exportPathMap`-functions, since it instead adds it after that function is run. While it is possible that someone is relying on this to exist, it is to my knowledge undocumented and also unlikely to be used for anything but merging it into the custom pathMap. Since this would now merge `undefined` which would result in it being added later on anyway, I deemed it safe, but would be happy to undo that part of the PR if necessary as it was only cleanup. **Examples** As a way to demonstrate what this PR does, this is how examples changed: * `basic-export` - Behaviour is unchanged, still has a `404.html` * `with-static-export` - Now has a `404.html` |
||
|---|---|---|
| .. | ||
| next | ||
| next-bundle-analyzer | ||
| next-mdx | ||
| next-server | ||