Tags: anton-karlovskiy/next-on-netlify
Tags
Publish v2.4.0 - Add support for base64 encoding in responses returned from SSR pages and API endpoints - Reduce the number of rewrites generated by skipping SSG & HTML pages with static routing. These pages are routed automatically by Netlify ([netlify#26](netlify#26)) - Limit the default number of lines of build output to 50. More or fewer lines can be shown by running `next-on-netlify` with the option `--max-log-lines XX`. See `next-on-netlify --help` and [this comment](netlify#26 (comment)). - Remove workaround for making `404.html` work with `netlify dev`. The workaround is no longer required because [`netlify dev` has been patched](netlify/cli#1159).
Publish v2.3.2 - Fix: Bump elliptic to v6.5.3 to fix [CVE-2020-13822](GHSA-vh7m-p724-62c2)
Publish v2.3.1 - Fix: Correctly get distDir from `next.config.js` when config is a function ([netlify#25](netlify#25))
Publish v2.3.0 - Add support for [NextJS Preview Mode]( https://nextjs.org/docs/advanced-features/preview-mode) ([netlify#10](netlify#10)) Note: NextJS Preview Mode does not work on pages that are pre-rendered (pages with `getStaticProps`). Netlify currently does not support cookie-based redirects, which are needed for supporting preview mode on pre-rendered pages. Preview mode works correctly on any server-side-rendered pages (pages with `getInitialProps` or `getServerSideProps`). - Use `multiValueHeaders` in Netlify Functions for incoming requests and for outgoing responses. This offers many benefits over plain `headers`, such as setting multiple cookies within one response.
Publish v2.2.0 - Add support for defining custom redirects in a `_redirects` file at the project root directory. Unlike redirects specified in your `netlify.toml` file, the redirects from the `_redirects` file take precedence over those generated by `next-on-netlify` ([netlify#21](netlify#21))
Publish v2.1.0 - Add support for [NextJS optional catch-all routes]( https://nextjs.org/docs/api-routes/dynamic-api-routes#optional-catch-all-api-routes ) ([netlify#15](netlify#15)) - Fix: An `index.js` page with `getStaticProps` no longer causes `next-on-netlify` to fail ([netlify#18](netlify#18)) - Fix: Catch-all routes now correctly require that at least one URL parameter is present (unlike optional catch-all routes) ([479b7e7](netlify@479b7e7)) - Fix: Data routes now correctly work for pages with catch-all routing ([0412b45](netlify@0412b45))
Publish v2.0.0 - **Breaking: You must change your `netlify.toml` configuration for next-on-netlify v2.0.0.** Please look at the README for the latest configuration. `next-on-netlify` now builds pre-rendered pages and static assets in `out_publish`. Netlify Functions for SSR pages are built to `out_functions`. - Add support for `getStaticProps` (netlify#7) - Add support for `getStaticPaths` with and without fallback (netlify#7) - Add support for `getServerSideProps` (netlify#7) - Query string parameters are now correctly passed to Next Pages and API endpoints (netlify#9) - Response headers are now correctly set (netlify#9) - When a user encounters a 404, `next-on-netlify` now display the NextJS 404 page rather than Netlify's default 404 page. You can customize the NextJS 404 page. (netlify#2) - Every page with server-side rendering is now converted to a stand-alone Netlify Function. Previously, all SSR pages were bundled in a single Netlify Function. - `next-on-netlify` now prints out which pages are being converted to Netlify Functions for SSR, which pages are served as pre-rendered HTML, and the redirects that are being generated. - Adding custom redirects via a `_redirects` file in the project root is no longer supported. Let me know if you want this back. Or define your redirects in `netlify.toml`.
PreviousNext