Adam Brauer

Building on the workaround found by @Gawdfrey (🙏), if you simply wanted to exclude all api routes from middleware, seems you could do something like this: ``` export const config...

Hi @pzi @ChrisManganaro - We investigated a similar (`withSitecoreContext` HOC) issue and we narrowed it down to what appears to be a bug introduced in Next.js version 12.1.6. The fix...

Hi @monkey-ldb. This is a great suggestion. I've added this to our backlog to prioritize. We also gladly accept PRs if you're willing. Check the [contributing guide](https://github.com/Sitecore/jss/blob/dev/CONTRIBUTING.md) as it has...

Hi @petedavisdev - Thanks for the information, I've added this to our backlog to investigate / fix in a future release. Just out of curiosity, did you figure out why...

Fixed by #1150

Hi @kashifovrlod! Thanks for the information, I've added this to our backlog to investigate / fix in a future release. We also gladly accept pull requests if you'd like to...

@thaiphan @ChrisManganaro @pzi Thanks for the feedback, I've added this to our backlog to investigate / fix in a future release. Just taking a quick look through the details, I'd...

Hi @monkey-ldb - Yes, we have this on our roadmap and are actively working on this effort, planned for an upcoming release (TBD).

Hi @moh4sa - We are targeting to include this in a release of JSS before the end of the year.

Hi @coreyasmith - Can you check that you are using `http:\\localhost:3000` for the next.config.js `assetPrefix` (by default this originates from the `PUBLIC_URL` environment variable)? Latest versions of Next.js should [derive...