Skip to content
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

Package Compatibility #287

Open
christianjuth opened this issue Dec 9, 2024 · 4 comments
Open

Package Compatibility #287

christianjuth opened this issue Dec 9, 2024 · 4 comments

Comments

@christianjuth
Copy link

christianjuth commented Dec 9, 2024

This issue aims to outline all the package compatibility issues with One as One approaches it's stable release.

I will update the issue as I become aware of other packages causing issues.


Expo packages

Package Description of Issue Tested Version(s) Reproduce Link Fixed
expo-image When I run yarn dev I get "The JSX syntax extension is not currently enabled" caused by expo using .js files instead of .jsx.
expo-blur When I run yarn dev I get "The JSX syntax extension is not currently enabled" caused by expo using .js files instead of .jsx. 13.0.2 1.1.341
expo-asset #301
@lexical/react #303

In theory, we should be able to fix these using One's Vite config deps (see docs). Some messages on One Discord suggest there might be a second layer to this issue.


Misc

Package Description of Issue Tested Version(s) Reproduce Link Fixed
react-native-reanimated-carousel "x Build failed in 6.52s, error [vite:json] [plugin vite:json] virtual:rn-internals:react-native/package.json: Failed to parse JSON file."
@zetavg
Copy link
Collaborator

zetavg commented Dec 13, 2024

expo-blur should work now with the fixes included in 1.1.341 👍

@clayrisser
Copy link
Contributor

Is there an exposed api that will allow people to get their own package support working without waiting for official support?

@clayrisser
Copy link
Contributor

I guess that's what the deps config is for.

@natew
Copy link
Collaborator

natew commented Dec 16, 2024

@lexical/react should work now with 1.1.344

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

No branches or pull requests

4 participants