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

Generate node.js compatible modules #285

Closed
2 of 3 tasks
vsmenon opened this issue Aug 7, 2015 · 6 comments
Closed
2 of 3 tasks

Generate node.js compatible modules #285

vsmenon opened this issue Aug 7, 2015 · 6 comments

Comments

@vsmenon
Copy link
Contributor

vsmenon commented Aug 7, 2015

This has been suggested a few times. Opening this as a tracker.

Some blockers:

@jmesserly
Copy link
Contributor

IMO, ES6 isn't really a blocker ... nodejs is going to support it. So it's a backporting issue: do we want to support older node versions, or do we want this before nodejs is finished with ES6. But in that case, could we just use an existing ES6->5 transpiler for that?

dart:io and friends ... no JS implementation for these

yeah. tricky part there is I'm not sure how the test coverage is for dart:io these days. Used to be not great. I guess Pub covers it pretty well though, so maybe Pub's tests can work as a dart:io test suite.

@devoncarew
Copy link
Contributor

Adding the atom label to this. It's not a blocking issue - I'm able to use the existing module system w/ some code-gen - but we've talked about it enough in the context of atom that I thought I'd add the tag.

@jmesserly
Copy link
Contributor

Adding the atom label to this. It's not a blocking issue - I'm able to use the existing module system w/ some code-gen - but we've talked about it enough in the context of atom that I thought I'd add the tag.

yeah, +1. Even if you can work around it, we should still make it so you don't have to/can get rid of the workaround :)

@jmesserly
Copy link
Contributor

Fixed in 393c2b3 🎉

@jmesserly
Copy link
Contributor

I'll open a bug for dart:io node wrapper.

@jmesserly
Copy link
Contributor

#436 for dart:io

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

No branches or pull requests

3 participants