-
Notifications
You must be signed in to change notification settings - Fork 1.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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[馃悶] Version 1.5.3 build is broken: Cannot load native addon because loading addons is disabled #6223
Comments
@ohkimur can you stay on 1.5.2 until we fix it |
csr: true will be fixed in next release #6292 |
Ah and the dlopen issue is separate because now we ship a binary from Linux and it tries to use it in stackblitz. So we need to be more careful about that. |
What can I do here ? |
@wmertens you can outline what @JerryWu1234 can do 馃檶 |
@PatrickJS Do we have any update on this topic? I'm wondering if there's something I could help with. I see the vite-demo still is failing to compile. The same happens still when I update to |
@wmertens is the only one with enough context on what to fix here |
This is a cosmetic error. It shows that and then it uses wasm instead. I have a fix already but it's in a PR that's blocked right now, I'll add it separately when I get a chance. |
@wmertens Can you mention me in the PR? I'd like to take a look and understand the problem deeper if possible. |
Which component is affected?
Qwik Rollup / Vite plugin
Describe the bug
Starting with v1.5.3 the vite build fails. This fails in a few different environments, including the official
vite
template forqwik
. Check it out here.Also, starting with this version,
qwik
doesn't respect custom rollup configs from vite properly, including customdir
, andentryFileName
options.NOTE: I'm working on a very big design system that supports all the major frameworks including
qwik
. For each one of them I build todist
. It would be great to be able to keep doing this for qwik.Reproduction
https://stackblitz.com/edit/vitejs-vite-zyuten?file=package.json
Steps to reproduce
No response
System Info
Additional Information
No response
The text was updated successfully, but these errors were encountered: