Skip to content

Commit

Permalink
docs: add execution order limitation to Netlify docs (#40)
Browse files Browse the repository at this point in the history
  • Loading branch information
orinokai authored Dec 19, 2024
1 parent af52ef0 commit dab4a6f
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions pages/netlify/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,8 @@ Currently, Netlify's Next.js adapter has the following limitations:

- **Rewrites in your Next.js configuration can’t point to static files in the `public` directory.** If you create `beforeFiles` rewrites in your `next.config.js`, they can’t point to static files in your site’s `public` directory. You can use middleware rewrites as an alternative.

- **Headers and Redirects are evaluated after middleware.** If you need to maintain the execution order specified in the Next.js [docs](https://nextjs.org/docs/app/building-your-application/routing/middleware#matching-paths) you will need to configure your [headers](https://docs.netlify.com/routing/headers/) and [redirects](https://docs.netlify.com/routing/redirects/) outside of Next.js using our platform primitives.

- **Netlify Forms compatibility:** Using Netlify Forms with the current adapter [requires a workaround](/netlify/forms).

### pnpm support
Expand Down

0 comments on commit dab4a6f

Please sign in to comment.