CSS.escape compatibility issues with Vite + Rolldown - seeking alternatives #1594
hranum
started this conversation in
Feature Requests / Ideas
Replies: 3 comments 1 reply
-
I was under the impression that rolldown vite is going to be a "drop in replacement", so perhaps this is something that will be addressed before it goes live? |
Beta Was this translation helpful? Give feedback.
1 reply
-
I am getting this error: With the path above applied, the error goes away and everything works. Upstream this issue exists: mathiasbynens/CSS.escape#12 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Will be resolved for Bits UI shortly #1608 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone! 👋
I'm running into an issue with the
css.escape
dependency introcued in 1.6.1 when using Vite with the new Rolldown bundler. Getting this error in the console when running the app after bundling.css.escape
was introduced to replaceencodeURIComponent
in 1.6.1 1482The problem seems to be that Rolldown handles global object resolution differently than traditional Rollup, causing the UMD wrapper in
css.escape
to receive undefined as the root parameter instead of the expected global object.Tried different rollup options to no avail so I've temporarly patched
css.escape
Just wondering if this is something for bits-ui to keep in mind when rolldown eventually becomes standard, and if there could be alternatives to css.escape instead of shimming globalThis etc.
What's your thoughts?
Beta Was this translation helpful? Give feedback.
All reactions