-
-
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
devalue import fails with adapter-node #6394
Comments
On first deploy it complained about "cannot find package devalue", and then I remembered that I had to do the workaround of installing it. I copied the package.json lines out of my other project with the workaround, and you are correct it was version 2 of devalue. I guess the real issue is that it did not find a devalue package installed after the initial build step. |
Are you still seeing this with the latest versions of everything? If so, please provide a minimal reproduction as a clonable repo. |
This is fixed with the latest version |
Newest version fixes everything. Thank you! Btw, the new and improved dependency bundling is really sweet! |
I have the same problem. can anyone tell which version introduced this problem? I need to go back to before that. Cant go forward as I get other issues |
Hi @jesperordrup , I am facing the same issue and was able to make it work with |
It sounds like you might be able to solve it by installing |
Describe the bug
Had to change the line in build/server/index.js from
import { devalue } from "devalue"
to
import devalue from "devalue
to get my app to start after updating to @sveltejs/kit version "1.0.0-next.448" and @sveltejs/adapter-node version "1.0.0-next.87"
Reproduction
Build an app with standard adapter-node server and start with
node build/index.js
Logs
System Info
Severity
serious, but I can work around it
Additional Information
Easy workaround but, if user is not aware it will block them from deployment. Also the error message solution of changing to
fails. Instead you need to do
import devalue from "devalue"
.The text was updated successfully, but these errors were encountered: