fix: enable using the direct queue for isr

[james-elicx]

• Allow use of direct for the queue.
• Enable ISR tests for app router e2es.
• Fix e2e isr route so it imports the manifest for the revalidation test.

[changeset-bot]

🦋 Changeset detected

Latest commit: 4fb97c3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@opennextjs/cloudflare	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

Open in Stackblitz

pnpm add https://pkg.pr.new/@opennextjs/cloudflare@319

commit: 4fb97c3

[vicb]

Awesome 🎉

I'll try to review the PR tomorrow afternoon!

[conico974]

While this will work and could be used right now to make ISR work, i think a better solution long term would be to use a queue system for deduplicating the revalidation.

With the direct queue, once a page is stale, every request for this page (while it is revalidating and available worldwide) will trigger a new revalidation.
KV will probably throw a lot of error because of the 1s write per key limitations

[james-elicx]

While this will work and could be used right now to make ISR work, i think a better solution long term would be to use a queue system for deduplicating the revalidation.

With the direct queue, once a page is stale, every request for this page (while it is revalidating and available worldwide) will trigger a new revalidation. KV will probably throw a lot of error because of the 1s write per key limitations

Agreed, I had wrote on the issue that we should do it as an additional piece of work separately to this - both should be available for people to use ideally.

[vicb]

Can you rebase and try to upstream the change?

[james-elicx]

Can you rebase and try to upstream the change?

I've opened opennextjs/opennextjs-aws#728 to upstream it.

[vicb]

Thanks for the update 🚀