You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have a dependency that needs to be excluded from the bundle, so I mark it as external in svelte.config.js like so:
This correctly gets excluded in the .svelte-kit build, but it gets included in the adapter build's output.
Describe the solution you'd like
Use the kit.vite.esbuild settings from svelte.config.js in the adapter build
Describe alternatives you've considered
I noticed the node adapter excludes pkg.dependencies - maybe we just need to do the same for Vercel adapters? Is there a reason for doing that in one adapter and not another?
How important is this feature to you?
Important, I'm unable to deploy until I can exclude this dependency.
The text was updated successfully, but these errors were encountered:
This patch attempts to solve sveltejs#1706
We pass through the esbuild configurations in svelte.config.cjs into the
esbuild step of the vercel adapter.
This is primarily to solve the case where we have external packages that
are skipped by esbuild in adapater-node, but not adpater-vercel.
Is your feature request related to a problem? Please describe.
I have a dependency that needs to be excluded from the bundle, so I mark it as external in svelte.config.js like so:
This correctly gets excluded in the .svelte-kit build, but it gets included in the adapter build's output.
Describe the solution you'd like
Use the
kit.vite.esbuild
settings from svelte.config.js in the adapter buildDescribe alternatives you've considered
I noticed the node adapter excludes pkg.dependencies - maybe we just need to do the same for Vercel adapters? Is there a reason for doing that in one adapter and not another?
How important is this feature to you?
Important, I'm unable to deploy until I can exclude this dependency.
The text was updated successfully, but these errors were encountered: