- move execa to prod dependency
- NoN is still deprecated but @sls-next dependency was causing issues
- add support for background functions in api pages only (#171)
- remove next as peer dependency (#167)
- add watch mode (#162)
- Fix: next 10.0.6 changed prerender-manifest for i18n (#163)
- Chore: support node 15
- Fix: image url in imageFunction (#159)
- Put back next/image support (#158)
- Fix: strip file extension when checking if route is dynamic (#155)
- Fix: prevent copy of .public to .public (#146)
- Fix: add check if pages-manifest exists before reading (#147)
- Fix: throw error if .next/static cannot be found (#148)
- Fix: remove unnecessary * from headers rule (#152)
- Fix: check existence of dirs before reading them in file tracking logic (#150)
- Revert next/image support until jimp module issue is resolved (#149)
- Revert route/redirect sorting logic to static then dynamic (#145)
- Fix: incorrect headers syntax & broken local cypress (#144)
- Fix: failing windows test for file tracking (#142)
- Fix: file tracking bug where publishDir was being used for functons cleaning too (#ba41f)
- Fix: fallback blocking would cause builds to crash (#139)
- next/image initial support (#138)
- generate headers file to override static chunks cache control (#141)
- track NoN files for configured dirs to clean before each run (#134)
- Hotfix: index gsp pages caused builds to fail in i18n (#75)
- Hotfix: update logic for allowing colliding route redirects (#130)
- Support for i18n in Next 10 (#75)
- dependabot: node-notifier from 8.0.0 to 8.0.1 (#125)
- Expose Netlify function params as netlifyFunctionParams (#119)
- Fix: local cypress cache control (#118)
- Fix: add res.finished to createResponseObject (#117)
- Fix: Windows support (#101)
- Improve logs for specified functions/publish dirs (#100)
- Fix: don't empty publish/function paths unless they're default (#94)
- Fix: add support for res.redirect in API routes (#93)
- Remove next-aws-lambda dependency (now inlined) (#92)
- Fix: Node.js version in CI (#91)
- Upgrade version range of
next
(#90) - Configurable functionsDir and publishDir (via exported func only) (#89)
- Support for Node 10.17.0 (#84)
- CI tests (#83)
- Hotfix: no-cache Cache-Control for preview mode (Commit)
- README updates
- Update isRootCatchAllRedirect condition (#77)
- Support for SSG Preview Mode (#50)
- Expose core setup logic to be required as a package (#64)
- Miscellaneous README cleanup
- README rebrand
- Fix: update logs to correct path constants in prepareFolders (#58)
- Fix: show experimental-serverless-trace target option in README (#59)
- Fix: x-forwarded-host is undefined on Netlify (#54)
- Fix: No-op redirect for root catch-all page chunks (#52)
- prettier pre-commit hook
- Fix: broken redirects for optional catch-alls (#47)
- Copy host property from headers to multiValueHeaders #44
- More support for ISR (getStaticProps with revalidate) Discussion / Commit
- Fixed redirect for index with getServerSideProps #39
- 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
. Seenext-on-netlify --help
and this comment. - Remove workaround for making
404.html
work withnetlify dev
. The workaround is no longer required becausenetlify dev
has been patched.
- Fix: Bump elliptic to v6.5.3 to fix CVE-2020-13822
- Fix: Correctly get distDir from
next.config.js
when config is a function (#25)
-
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 withgetInitialProps
orgetServerSideProps
). -
Use
multiValueHeaders
in Netlify Functions for incoming requests and for outgoing responses. This offers many benefits over plainheaders
, such as setting multiple cookies within one response.
- Add support for defining custom redirects in a
_redirects
file at the project root directory. Unlike redirects specified in yournetlify.toml
file, the redirects from the_redirects
file take precedence over those generated bynext-on-netlify
(#21)
- Add support for NextJS optional catch-all routes (#15)
- Fix: An
index.js
page withgetStaticProps
no longer causesnext-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)
- 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 inout_publish
. Netlify Functions for SSR pages are built toout_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 innetlify.toml
.
- Add support for custom NextJS build directory: If
distDir
is specified innext.config.js
, next-on-netlify will use that directory. If nodistDir
is specified, it will look for the default directory (.next
).
- Add README
- Add CHANGELOG
Initial release of next-on-netlify