-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Meteor 3.0 support #12
Comments
Thank you for submitting this issue! We, the Members of Meteor Community Packages take every issue seriously. However, we contribute to these packages mostly in our free time. If you think this issue is trivial to solve, don't hesitate to submit Please also consider sponsoring the maintainers of the package. |
This is on my todo list but changes to move away from Fibers/Futures will be necessary. Unfortunately my current paid workload has not allowed me to explore what these changes might be as of this time. |
Update: I've started work on this. Not sure how fast it will progress as it will require updates across dependencies as well. Will try to update here as I make progress. |
Update 2: Making some pretty good progress with this packages, as well as picker and inject-data which this relies on. At this point I'm working on satisfying the last 3 tests, 1 on the server and 2 on the client. |
Update 3: Still progressing on this. All server tests pass and data is getting properly sent to the client for both null publications and subscriptions that run on the server via using fast-render's publication mechanism. The final issue will be solving calling Meteor.subscribe on the server for things like server rendering, since it there is no real way to await a subscribe call, and the API needs to match the client side API so that code can match isomorphically. I'm starting to run short on free time at the moment and so I'm going to estimate that we are looking at around 3 weeks before I can get this fully completed. |
@copleykj hello, I send you an email, maybe you not receive I love the package |
Hey @welkinwong, I'm currently working on this, I just have one race condition that I'm having an issue figuring out how to correct it. Not sure how long it will take, but I will keep trying till I figure it out. |
could you share what is blocking you @copleykj ? |
@henriquealbert I think at the moment I'm in a good spot. I'm in the process of fixing some tests and potentially moving them from tinytest to mocha so that they all run on the same driver. The one thing I'm not sure about how to handle is server side Meteor.subscribe, but that only comes into play for server rendering and I think issuing a release that doesn't initially support SSR might be ok and then that can be added once I get my head around how waiting on subscribe functions can be handled. |
Most everything is in order here... I've rewritten all the tests and they all pass. I've published both |
I have a project without any SSR that I'd love to test this on... I spent a ton of time re-writing fast render to use async / await instead of fibers, but haven't been able to reliably get the subscribe to work on the server side so the inject-data outputs into the page. I am hoping that your work @copleykj will allow me to ditch my broken code 😆 . |
@wreiske so I'm still not able to publish the beta here due to the livedata constraint issue I'm having. That being said the 2 packages that this relies on did publish and so if you'd like to try it, you should be able to clone this repo into a packages dir and test it. One caveat may be the need to the project to be running on Meteor 3, but as long as that is the case this should work. |
OK - I checked out the v5 branch. I'm not sure if the onAllRoutes is working.
I have simply:
... and ...
I see in my logs:
|
Figured it out!!!
🥳 |
Awesome 😎 Let me know if you find any other issues 🙏 |
Version 5.0.0-beta.0 has been published. I'm going to close the few 3.0 support issues. If you find any issues that aren't related to SSR please open new issues for them. |
hope support meteor 3.0 🥺🥺🥺
The text was updated successfully, but these errors were encountered: