feat: d1 adapter for the tag cache

[james-elicx]

• Enable tag/path revalidation and next/after e2es for app directory example.
• Enable passing a function for the tag cache.
• D1 adapter for the tag cache, based on the AWS DynamoDB adapter.
• Extracts a manifest of build-time tags/paths and creates an sql file that can be used to stub D1.
• Adds the env.d.ts file to the tsconfig so that TypeScript recognises env vars defined in there.
• Bumps aws to return meta files from createAssets() opennextjs-aws#748

Docs PR - opennextjs/docs#66

[changeset-bot]

🦋 Changeset detected

Latest commit: f5d8133

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	Minor

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@320

commit: f5d8133

[conico974]

LGTM, nice work!!
To be perfectly honest, i'm still not 100% convinced that D1 is the perfect fit for this (at least not alone). The tag cache can be used in SSR for the fetch cache and i'm not sure if D1 can handle heavy workload for these cases.
It's probably fine in most cases but i still wanted to point this out

[vicb]

I added a couple comments.

IIUC we should first get opennextjs/opennextjs-aws#717 merged and then this PR?

Even if using D1 is not ideal, we can keep iterating before 1.0 but it would be nice to unblock people as early as we can.

WDYT @conico974 @james-elicx ?

[conico974]

IIUC we should first get opennextjs/opennextjs-aws#717 merged and then this PR?

Not necessarily, but it would avoid people getting a bunch of errors if they use this with page router only. And it avoids checking the cache tag for page router.

Even if using D1 is not ideal, we can keep iterating before 1.0 but it would be nice to unblock people as early as we can.

I agree, and it will allow to collect some feedback

[vicb]

@conico974

opennextjs/opennextjs-aws#717

What's missing for this PR to get merged? Do you have an approximate ETA in mind?

[conico974]

@vicb it should be ready actually, i just requested a review

[james-elicx]

IIUC we should first get opennextjs/opennextjs-aws#717 merged and then this PR?

I thought we had agreed that we would add both modes with users having the option of deciding which they want to use, so there shouldn't be any dependency on the new mode for this PR. Unless we want to add the other mode in this PR as well and release both modes at the same time?

[vicb]

IIUC we should first get opennextjs/opennextjs-aws#717 merged and then this PR?

I thought we had agreed that we would add both modes with users having the option of deciding which they want to use, so there shouldn't be any dependency on the new mode for this PR. Unless we want to add the other mode in this PR as well and release both modes at the same time?

I was referring to "Not necessarily, but it would avoid people getting a bunch of errors if they use this with page router only. And it avoids checking the cache tag for page router."

[vicb]

Thanks a lot for creating this PR and all of the updates!μ

LGTM, a couple minor comments.

🚀