RealOrangeOne commented 5 years ago

Unfortunately, due to a variety of reasons, I find myself unable to commit time to maintaining react-native-mock with the effort required it deserves. (The commit graph clearly shows it's been a while since I've had the time!)

120, which is my most recent work, is definitely the direction I want the project to progress. Maintaining a functioning mock of `react-native` is a lot of work, and it's more efficient to use the `react-native` code itself!

I notice there are a lot of forks of this repo, and I'd love to help those be upstreamed and help everyone!

If you're interested in helping maintain react-native-mock, reach out! I really don't want this project to die!

chakrihacker commented 4 years ago

If you are interested, you can move to react-native-community

RealOrangeOne commented 4 years ago

Huh, that could definitely help the project continue.

Definitely something i'd be interested in discussing! https://theorangeone.net/contact/

RealOrangeOne / react-native-mock

Maintainers wanted #168

120, which is my most recent work, is definitely the direction I want the project to progress. Maintaining a functioning mock of `react-native` is a lot of work, and it's more efficient to use the `react-native` code itself!

RealOrangeOne / react-native-mock

Maintainers wanted #168

120, which is my most recent work, is definitely the direction I want the project to progress. Maintaining a functioning mock of react-native is a lot of work, and it's more efficient to use the react-native code itself!

120, which is my most recent work, is definitely the direction I want the project to progress. Maintaining a functioning mock of `react-native` is a lot of work, and it's more efficient to use the `react-native` code itself!