I think we should loop @javascripter in or create a dedicated issue. Obviously this is an integration issue.
https://github.com/zaydek/experimental-react-strict-dom is now updated to use the API ...
Also having issues: created https://github.com/zaydek/experimental-react-strict-dom and also here's a quick video explaining the problem (video is slightly longer than one minute)
https://github.c...
I found in my [experimentation](https://github.com/facebook/stylex/discussions/849) that I cannnot merge themes in StyleX. This may be intentional behavior but it's not what I was expecting and @ne...
Quick follow up: Using the styles pattern worked. I also read https://github.com/facebook/stylex/blob/6df047c7933c765c7e7de552faa69d569a152fb4/apps/docs/docs/learn/06-recipes/05-merge-themes.mdx an...
Thanks! I think themes are designed for a different use case than I may be imagining. My constraints are I want to be able to theme an app using runtime values where theme tokens cannot necesarrily...
I found in my [experimentation](https://github.com/facebook/stylex/discussions/849) that I cannnot merge themes in StyleX. This may be intentional behavior but it's not what I was expecting and @ne...
I found in my [experimentation](https://github.com/facebook/stylex/discussions/849) that I cannnot merge themes in StyleX. This may be intentional behavior but it's not what I was expecting and @ne...
I found in my [experimentation](https://github.com/facebook/stylex/discussions/849) that I cannnot merge themes in StyleX. This may be intentional behavior but it's not what I was expecting and @ne...
I guess I should mention that technically this is how to make TS happy:
```tsx
const bar = {
foo: "hello",
}
const foo = {
...bar,
foo: "hello",
}
```
But it also means that y...
> I agree that include should be documented. The reason is that the documented merging using stylex.props is done directly on the element, which conflicts with cleanly defining the styles of that e...
@aleksei-reznichenko Addding `overrides` to my `package.json` seems to silence the error. I also tried `*` for the version but it didn't work.
```json5
{
...
"dependencies": {
...
...
I think I'm having the same issue
```sh
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
...
My bad just old habits.
<img width="579" alt="Screenshot 2025-01-04 at 8 32 42 AM" src="https://github.com/user-attachments/assets/2723a235-3d55-499e-b30e-77be077040e4" />
### Describe the feature request
Whenever I write involved StyleX code, I need to destructure types from `"@stylexjs/stylex/lib/StyleXTypes"` as opposed to `"@stylexjs/stylex"`.
For example:
...