Skip to content

Conversation

MoOx
Copy link
Contributor

@MoOx MoOx commented Apr 12, 2025

Until facebook/stylex#856 is merged and released, this is kind of the only option to be able to write imports like defined in a tsconfig file.

…/babel-preset

Until facebook/stylex#856 is merged and released, this is kind of the only option to be able to write imports like defined in a tsconfig file.
@necolas
Copy link
Contributor

necolas commented Apr 12, 2025

This just needs to be fixed in stylex

@necolas
Copy link
Contributor

necolas commented Oct 11, 2025

Remind me what aliases are needed for? Is it only for resolving the vars files?

@MoOx
Copy link
Contributor Author

MoOx commented Oct 11, 2025

Basically writing absolute imports like @/components/* for local code, following ts config. Stylex doesn’t yet auto detect paths from tsconfig file so alias is the only way so RSD can resolve paths properly when using this arobase import styles (a common thing this days as it’s in lot of default tsconfig (eg: next default template))

@necolas
Copy link
Contributor

necolas commented Oct 11, 2025

Yeah but what features require import resolution? Just the ones relying on *.stylex.js files existing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants