[Question] Is the project still under development?

[piotrfalba]

I see that there are a lot of pull requests that are not merged or discussed.
It wouldn't be cool if the project just died :(

[Mokto]

Hi @piotrfalba.

I can give access to any person willing to help contribute on the project.

[charpeni]

The project isn't dead, it's just hard to keep it synced with Meteor.

Feel free to help in pull requests or discussions, I'll be happy to merge reviewed PRs.

[ardatan]

Now, the official meteor client can be used on react-native w/ meteor-client-bundler. You don't need any 3rd party packages anymore. You can check out this boilerplate, and refactor your code by using official Meteor React integration library (meteor/react-meteor-data). By using this method, you can share the code between client and server.
If @inProgress-team would welcome and feel tired about keeping this project up-to-date with Meteor, they can share this repository in their README. Thanks!
We just updated this repository.
https://github.com/DAB0mB/ReactNativeMeteorBoilerplate

[jeffreyflynt]

@ardatan I am not understanding. We remove this package and install meteor-client-bundler? You state we don't need any 3rd party packages anymore. Is this assuming we were already using meteor-client-bundler?

[ardatan]

https://medium.com/@ardatan/connecting-react-native-and-meteor-w-o-any-3rd-party-library-in-2018-3e784d33acb0
@jeffreyflynt meteor-client-bundler is not a runtime package. It is a bundler package which bundles Meteor's own client packages such as react-meteor-data and minimongo (not 3rd party) in order to use with non-Meteor projects like React Native. If you see the repository and the blog post, you will understand better. So it is not something like you import in your projects.

[foysalit]

Hey @Mokto and @charpeni great work on the lib so far. I'd be more than happy to help out with the chores if you could give me access to the repo? do you have a slack or any other chatgroup to discuss stuff?

[lc3t35]

Hello, I think we face many issues that aren't fixed despite many PR submitted but not published. Maybe it is time to let new people handle the project and our beloved creators @Mokto and @charpeni have a deserved pause ?
I would like to know if @foysalit @elie222 @Pagebakers @kuserich (from https://gitter.im/react-native-meteor/Lobby) or someone else not listed would like to take the lead on this repo, or simply help to fix issues.
Thank you

[xvonabur]

Hello! I've forked react-native-meteor and updated its dependencies. Not exactly this original repo, but copleykj/react-native-meteor version.

I had to fork minimongo-cache also, because it's using very old lodash version. Anyway, here are my forks: https://github.com/xvonabur/react-native-meteor and https://github.com/xvonabur/minimongo-cache. I've also created temporary npm packages for them, so right now no vulnerabilities on npm install.

Just ping me if you need a PR to update dependencies for this repo.

[pisacode]

@ardatan great work, I have replaced react-native-meteor with the meteor client bundler on my existing app. It seems to work ok but every time I killed the app the logged-in user would be erased and had to log in again. Couldn't find a way to sustain the user.

[vforvasile]

any updates on this thread?

[adamgins]

We use it in production.

[lc3t35]

@adamgins did you update anything or fork the repo to include unmerged PR or patch it ?

[adamgins]

We had to fork it to handle some specific use cases relevant to our app.. and we patch that fork as needed.

@Diwei-Chen any additional info pls?

[lc3t35]

@adamgins is it this fork : Buzzy-Buzz@49938a9 ?

[foysalit]

I have contributed a couple of commits to @xvonabur 's fork and they recently merged it. might want to check that out @vforvasile I'm using that fork in production and can't complain.