@alawi Yes, you’ve got the point.
I’m not thinking of replacing Node with Deno, but of making a modernized version of Meteor, which fixes some of the current pain points. I see it as a possibility to make a clear cut with obsolete concepts like Fibers (superseded by Promises and async/await) and Atmosphere packages (or maybe a rebirth of them in a new way, as I see some advantages of them over NPM). And it could be the step to convert the code base to TypeScript.
This could be the long awaited Meteor version 2.0 (and in this case not only for marketing purposes).
Meteor 2.0 a.k.a. PlutoJS 