-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Bad publish in @sveltejs/[email protected] breaking all builds (Netlify Vercel etc) #8530
Comments
i suspect this affects all the other adapters as well as i can see adapter-vercel has the same issue |
Same issue with Vercel
|
If anyone else finds this, in the Vercel camp, your workaround is
I suspect
would also work but I haven't tested |
excelent timing for starting to learn svelte to get a buggy adapter-node package with missing file, frustration is through the roof |
@k0d3r1s bro chill - there's a workaround above, besides, this only affects your ability to deploy to Vercel (or Netlify). You can still fire up |
@arackaf nope, i'm new to frontend so i'm not doing ts version for learning but js one. locally |
@k0d3r1s welcome to front-end development, where everything is held together by the heroic, usually unpaid efforts of OSS maintainers. Expect frustrating errors from time to time, and expect to be capable of searching, poking around, and being willing to figure out how to fix. If that's too much for you, then this might not be the best career field for you. Either way, showing up in GitHub threads talking shit like this is a great way to wear out your welcome, and ensure nobody will ever want to help you. |
For everyone else, my purported workaround above ... stopped working. And pinning to "@sveltejs/adapter-auto": "1.0.0" also failed to work. Anyone know how to work around this? |
@arackaf i expressed my thoughts. how is that talking shit? as this is an obvious bug, are people not allowed to complain? i get that frontend packages are buggy mess but that doesn't mean people need to write only good things about it |
@k0d3r1s Go vent your frustrations on your personal blog or social media, not in the maintainer's GitHub thread |
Ok this seems to work for me
kill your node_modules, and your lock file, and re-install, and that should hopefully work |
Yep, same problem with |
|
#8519 this is reason :) |
Again and again and again... |
The npm package is still at 1.0.1 which breaks the Vercel build. Any chance of a release with @dominikg 's fix? The solution #8530 (comment) works, but is not a permanent fix because manually installing the adapter defeats the purpose of adapter-auto. |
@dominikg looks like the release didn't happen because the last
I don't know |
Never mind, it sounds like the auto adapter did not need fixing. https://unpkg.com/@sveltejs/[email protected]/package.json The auto adapter does not directly depend on any of the other adapters. The versions of the other adapters do not end up in your lockfile unless you directly install them. If you are facing an issue still while using the auto adapter, I'm guessing Vercel is caching your build because your checked-in code has not changed. |
Describe the bug
fyi @Rich-Harris - #8522 broke adapter-netlify because the index.js stopped being published. see below
noticed my builds started failing 1hr after adapter-netlify 1.0.2 was published
adapter-auto gave this error:
then installing adapter-netlify gave this:
Reproduction
https://app.netlify.com/sites/swyxkit/deploys/63c33bd649e9cb0009b443fe
Logs
then
Severity
blocking all usage of SvelteKit
Additional Information
No response
The text was updated successfully, but these errors were encountered: