Using it without expo project ?

[alexzajac]

Using it without expo project ?

[juddey]

Hmm, this line causes the issue that you've found @jigartankhupp

import { LinearGradient } from "expo";

It looks like this component simply passes the props to the react-native-linear-gradient package underneath. The only catch is thatreact-native-linear-gradient uses native code so theres an extra install step. (The expo code insulates you from having to deal with the native deps)

@alexZajac Perhaps a non-expo and expo version of this package is needed, as long as we can reliably tell the difference between an expo and non-expo project.... Thoughts?

[alexZajac]

@jigartankhupp I will definitely create a version for non-expo projects, because as @juddey mentionned, using the react-native-linear-gradient package introduces some native code, which can't be included as such in an Expo project. Similarly, it's a pain for Expo projects to try including the native package.

[jigartankhupp]

@juddey Yes, correct it seems I can fork and install react-native-linear-gradient instead of LinearGradient from expo so it will be run on non-expo project. What do you think it will be the correct approach or not?

[juddey]

Yes @jigartankhupp thats certainly a solution for non-expo projects. I'm not familiar enough with expo though to know what to do to ensure compatibility.

[jigartankhupp]

Personally, I like to work on a non-expo project. I agree that expo provides good libraries and live reload on the app without a cable but losing native packages is not an ideal thing.

[efec89]

I'm waiting non-expo version too. Thanks :)

[alexZajac]

@jigartankhupp @efec89 I made the nonexpo package version, please check it out here, and give me some feedback because I'm not able to test it right now. If changes are required, let me know.

[jigartankhupp]

@alexZajac Thank you.

[tjboudreaux]

@alexZajac when I install react-native-skeleton-content-nonexpo, there isn't any source in the installed directory.

[alexZajac]

Hi @tjboudreaux !
The package doesn't include any src folder because as it's written in Typescript, I made the choice to only include the src directory on Github but not on the package itself.
The lib folder is the result of building the Typescript files to Javascript, and is included in the latest version.