At the beginning of 2015 when Babel was still called 6to5, I created the issue "Project Scope and Future" to solicit ideas and feedback from the community about my desire to generalize 6to5.https://github.com/babel/babel/issues/568 …
-
-
I see what you’re doing here.
- End of conversation
New conversation -
-
-
Peeps have already mentioned macros, so from me - custom tooling/build pipelines. Eg - a css-in-js macro, but applying the type checker to its intermediate output. Just not doable today without extreme effort. Oh and I’m always excited to use seb-source-software
-
That sounds... doable actually and very reasonable haha
- 1 more reply
New conversation -
-
-
entire babel/webpack stack ported to c++. so many people would pay for this.
-
What if a JS tool was fast enough?
- 3 more replies
New conversation -
-
-
more like: $ brew install sebs-things $ sebs-thing init $ sebs-thing install $ sebs-thing lint/bundle/compile
- 1 more reply
New conversation -
-
-
1. Type checking using same parser as bundler 2. Importable, type-safe syntax transformations/macros (like Rust procedural macros or OCaml ppx) that work everywhere (including tests)
-
Jest doesn't understand webpack loaders and vice versa. And worse, type checkers have no understanding of these transformations. Having these macros be type-safe would be huge (for example creating typed GraphQL queries).
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 
