-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
feat: add @stylexjs/stylex
example
#286
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 8182488:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First. stylex doesn't support esm module, so I use vite cjs plugin to transform it to esm. But I think in dev mode, server inline the code twice so make the error happened
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First. stylex doesn't support esm module, so I use vite cjs plugin to transform it to esm. But I think in dev mode, server inline the code twice so make the error happened
So, is it essentially the same as #110? |
CJS not supported is the vite issue. They suggest using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I investigated a while and I believe is plugin stylex bug with SSR
The plugin mostly works (https://github.com/HorusGoul/waku-stylex-demo), but I encountered an issue that prevented me from installing a Waku demo on the mono repo of the plugin to add tests to it. I believe it has to do with having multiple react versions in the same mono repo, for some reason, Waku is trying to pick the one from the top-level node_modules, see this PR: HorusGoul/vite-plugin-stylex#22 |
@stylexjs/stylex
example
/cc @dai-shi any idea? I think this is package manager behavior |
I'm not quite following. So, is it like this PR is working for @himself65 without dual package issue, but @HorusGoul has the dual package issue? |
What does it mean? It feels like this example has a limitation, or no? |
Just we have to add |
No. dual package issue happens on his repo. Not waku |
This reverts commit bbe07c4.
"pnpm": { | ||
"overrides": { | ||
"vite": "5.0.9" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even with this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so, some upstream package use different version of vite
No description provided.