-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
kit/packages/adapter-node/index.d.ts contains removed properties - entryPoint and esbuild #3175
Comments
@nstuyvesant Can you provide a GitHub repro or a StackBlitz link to setup the reproduction given? Looks like there's a lot of configuration needed for someone to take a look at the bug. |
The esbuild option and the I don't know what is the recommended way to migrate. But now you'll have to copy your custom server file and copy the dependencies or install dependencies on the production server. |
@jasonlyu123 - thanks. Looks like #2931 in 1.0.0-next.57 released 4 days ago will force me to refactor my configuration. An easy approach is to add to the build script to copy my server.mjs file to the build directory and make the appropriate adjustments to my start script and Procfile (for Heroku). As you pointed out, it looks like the only bugs here are in kit/packages/adapter-node/index.d.ts. These three lines should be deleted so it's clear the esbuild and entryPoint properties were removed: |
Closed via #3181 |
Describe the bug
Had a custom server working in prod using adapter-node 1.0.0-next.52. After updating to 1.0.0-next.58, I changed the
to
Builds seem to completely ignore my entryPoint in svelte.config.js. Full code is below.
Reproduction
svelte.config.js
/src/server.mjs
Logs
No response
System Info
Severity
blocking an upgrade
Additional Information
Cannot deploy the app because it lacks a content security policy now.
The text was updated successfully, but these errors were encountered: