-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Architecture #23
Comments
I like the idea, but I'm not sure how receptive existing users would be to installing an extra package dependency in order to keep this one working. Does Atom have any sort of mechanism for easing that situation? I'd still like to see how this base package would work, once there's something to look at. |
One of the main benefits of this approach will be standardising how to transpile things in Atom, and making it easier to write plugins to do so. Also organising all transpilers under a single
I'm not sure about that, there are some open PRs on this kind of thing already though, and also atom-package-deps. On a related note, I deprecated one of my packages recently with this code. Iv'e already written half of both packages, so I'll link to them here for you to look at once they're up. Hopefully then maybe I can add this along with a bunch of other existing Atom transpiler packages as plugins. |
@jdcrensh I finally got around to implementing this, and so here is that base package… atom-transpile. I also managed to finish a transpile-decaf plugin, to give an example. Also see #25, and a similar PR on another existing package here. |
I feel like this should be a plugin to some kind of
atom-transpiler
base package. I say this especially as I have another idea to put an Atom wrapper around decaf for transpiling CoffeeScript to ES6 in the opposite direction, or maybe that should be another source-preview package…@jdcrensh Any thoughts on this?
The text was updated successfully, but these errors were encountered: