Skip to content
This repository has been archived by the owner on Aug 31, 2018. It is now read-only.

If you support ES modules, you can beat node #21

Closed
SteveCruise opened this issue Aug 25, 2017 · 9 comments
Closed

If you support ES modules, you can beat node #21

SteveCruise opened this issue Aug 25, 2017 · 9 comments

Comments

@SteveCruise
Copy link

Please do it!

@TimothyGu
Copy link
Member

Node.js already has an open PR adding ESM support. Ayo is not interested in "beating" Node.js in this way, but instead by fostering a more welcoming community and focusing on things Node.js has historically neglected. See #15 for the core values of Ayo.js.

@addaleax
Copy link
Contributor

If I may add to that: It’s not that Node.js isn’t actively working on implementing this. If there turn out to be real shortcomings in Node’s implementation, then that’s certainly something worth discussing, but for now I agree with @TimothyGu and would say that focusing on this might not make the most sense.

@mearns
Copy link

mearns commented Aug 25, 2017

fwiw, I've been discussing the Ayo fork with my team. One thing that came up was that it's hard to imagine Ayo gaining a lot of momentum in the broader (non-contributing) community without any technical impetus to switch. While I agree that "beating node" probably does not make a lot of sense as a specific goal of this project, I do wonder if having some technical leverage over node could help boost the Ayo project to increase it's chances of success. After all, forming a better model for community, moderation, and governance doesn't do a lot of good if the project flatlines and its community dissolves.

@italonascimento
Copy link

After all, forming a better model for community, moderation, and governance doesn't do a lot of good if the project flatlines and its community dissolves

I guess a "better model for community, moderation, and governance" may be enough to make the project evolves really quickly, actually. That's why open source is so powerful, after all.

@Fishrock123
Copy link
Contributor

Fishrock123 commented Aug 25, 2017

Please see nodejs/node#14369 - I suspect we'd be inclined to also adopt that (compatibility), but it would be useful to discuss shortcomings (which I would probably take and coordinate with Bradley and Node too).

ESM implications are far larger than just Ayo and I'm entrenched enough in it to want to not screw it up on all fronts if possible.

@ghost
Copy link

ghost commented Aug 25, 2017

See also What is the “module” package.json field for? on SO for several additional links and some historical context.

@SteveCruise
Copy link
Author

Thanks for answer, thank you thank you very much. A V8 member said es modules is ready to used.

@bmeck
Copy link
Contributor

bmeck commented Aug 31, 2017

Let me know if any further questions on ESM exist.

@SteveCruise
Copy link
Author

no

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

No branches or pull requests

7 participants