Skip to content
This repository has been archived by the owner on May 10, 2021. It is now read-only.

Releases: netlify/next-on-netlify

v2.5.0

01 Oct 11:03
Compare
Choose a tag to compare
  • Copy host property from headers to multiValueHeaders #44
  • More support for ISR (getStaticProps with revalidate) Discussion / Commit
  • Fixed redirect for index with getServerSideProps #39

v2.4.0

06 Sep 06:19
Compare
Choose a tag to compare
  • 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 (#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.
  • Remove workaround for making 404.html work with netlify dev. The workaround is no longer required because netlify dev has been patched.

v2.3.2

06 Sep 07:20
Compare
Choose a tag to compare

Fix: Bump elliptic to v6.5.3 to fix CVE-2020-13822

v2.3.1

06 Sep 07:20
Compare
Choose a tag to compare
  • Fix: Correctly get distDir from next.config.js when config is a function (#25)

v2.3.0

06 Sep 07:21
Compare
Choose a tag to compare
  • Add support for NextJS Preview Mode (#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.

v2.2.0

06 Sep 07:22
Compare
Choose a tag to compare
  • 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 (#21)

v2.1.0

06 Sep 07:22
Compare
Choose a tag to compare
  • Add support for NextJS optional catch-all routes (#15)
  • Fix: An index.js page with getStaticProps no longer causes next-on-netlify to fail (#18)
  • Fix: Catch-all routes now correctly require that at least one URL parameter is present (unlike optional catch-all routes) (479b7e7)
  • Fix: Data routes now correctly work for pages with catch-all routing (0412b45)

v2.0.0

06 Sep 07:24
Compare
Choose a tag to compare
  • 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 (#7)
  • Add support for getStaticPaths with and without fallback (#7)
  • Add support for getServerSideProps (#7)
  • Query string parameters are now correctly passed to Next Pages and API endpoints (#9)
  • Response headers are now correctly set (#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.
    (#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.

v1.2.0

06 Sep 07:24
Compare
Choose a tag to compare
  • Add support for custom NextJS build directory: If distDir is specified in next.config.js, next-on-netlify will use that directory. If no distDir is specified, it will look for the default directory (.next).

v1.1.0

06 Sep 07:25
Compare
Choose a tag to compare
  • Add support for catch-all routes (#1, #5)
  • README: Fix instructions for local preview