Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Use process.env.NEXT_CACHE_HANDLER_PATH #145

Open
vicb opened this issue Nov 28, 2024 · 1 comment
Open

[FEATURE] Use process.env.NEXT_CACHE_HANDLER_PATH #145

vicb opened this issue Nov 28, 2024 · 1 comment
Labels
enhancement New feature or request triage

Comments

@vicb
Copy link
Contributor

vicb commented Nov 28, 2024

As noted by @conico974 in #143 (comment), Next now allows setting the cache handler via process.env.NEXT_CACHE_HANDLER_PATH

Consider using that for Open Next.

@vicb vicb added enhancement New feature or request triage labels Nov 28, 2024
@conico974
Copy link
Contributor

The way i see it we should do it in the aws repo.
We use the esbuild replacement plugin to apply this env variable on Next 15. This will also allow you to use this same replacement plugin to remove the require.resolve

In the future it would make sense to allow to customize this in the open-next.config.ts file directly, maybe add a build option that would allow to customize the esbuild build process itself.
We could even undeprecate (or reimplement) the experimentalBundledNextServer options and this would allow you to more easily fix stuff in NextServer directly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage
Development

No branches or pull requests

2 participants