-
Notifications
You must be signed in to change notification settings - Fork 80
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
drispy/gradient path doesn't match entrypoint #285
Comments
Ah, that's interesting, will look into it |
this might require removing the react-native field from package.json. i wonder if setting it to |
removing I think that's probably the best option until full support for |
Another idea would be adding |
yeah, not sure if there are downsides there. i guess everyone uses metro so could be fine |
Hi, i am hitting this issue as well. How could i make it work temporarily, while waiting for the fix ?
|
I did a clean yarn install, and it works. Kindly ignore my post |
Can you guys try |
@nandorojo Upgraded from drippy 3 to 4.3.5 and I am hitting this issue as well. |
👋 Thanks @nandorojo for an awesome lib!
I just upgraded from 3.x to 4.1 and after updating gradients to import from `dripsy/gradient' I get the following error when rendering a Gradient:
What i'm seeing, is that dripsy.gradient always exports from
build
dripsy/packages/dripsy/gradient/index.js
Line 1 in e8272cd
But in react-native, metro bundler will import from on
src
dripsy/packages/dripsy/package.json
Line 7 in e8272cd
This leads to two different copies of dripsy being loaded from
dripsy
anddripsy/gradient
so when I importDripsyProvider
it doesn't properly provide toGradient
.I'm a little surprised this hasn't come up yet in your usage of
Gradient
so I figure I must be "holding it wrong 🙃 . Am I missing something here? Thanks again!The text was updated successfully, but these errors were encountered: