Skip to content
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

Proof of concept: use aync_hooks #3

Closed
jankapunkt opened this issue Apr 13, 2021 · 2 comments
Closed

Proof of concept: use aync_hooks #3

jankapunkt opened this issue Apr 13, 2021 · 2 comments

Comments

@jankapunkt
Copy link
Contributor

We could start an important change, see: meteor/meteor-feature-requests#392

We would have to replace fibers with async hooks but we would then also be able to have Tracker being completely isomorphic.
https://nodejs.org/api/async_hooks.html#async_hooks_async_hooks

What do you think?

@jankapunkt
Copy link
Contributor Author

On the client we would have to make sure it runs with async functions

@harryadel
Copy link
Owner

harryadel commented Apr 13, 2021

I'm kind of in between surely this is the direction Meteor intends to embark on or so it seems but there's no telling of the future and how they'd implement things or how it'd affect us. Plus, there's no need to burden ourselves with additional baggage. The migration to NPM isn't easy as I had hoped because of the number of packages and tests/backwards compatibility.

Let me be clear, I'm not against your suggestion per se, it's just I think it's better to delay it until we have a stable NPM implementation then we can start later on to replace fibers with async_hooks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants