3 ms·
According to the article, and companion Babel blog ( https://babeljs.io/blog/2019/07/03/7.5.0 https://babeljs.io/blog/2019/07/03/7.5.0 ), this is usable already
by galacticdessert 7y ago
According to the article, and companion Babel blog ( https://babeljs.io/blog/2019/07/03/7.5.0 https://babeljs.io/blog/2019/07/03/7.5.0 ), this is usable already in combination with Babel.
Now, I understand how it might be desirable to NOT having to use Babel to run code, especially on Node. On the other hand, some amount of transpilation has become inevitable for js in the browser and I don't see this need going away soon, as JS evolves much quicker than browser adoption.
- IggleSniggle 7y agoYes, I know...but I live in TypeScript world where functional styles and types go together especially wonderfully. Babel solutions to TypeScript are messy and in some cases break the things I like about TypeScript. At least last I checked. But getting native TypeScript support is dependent on the feature actually making it into the official spec.
- jkoudys 7y agoBeen through that here, trying to get my whole dev env working nicely with both pipes and types. Very painful. I was surprised and a bit disappointed that pipelines seemed to be progressing years ago, then suddenly stalled. Nullish and optional chains are in ts already but pipelines aren't even on the horizon. From what I hear from tc39 people, method extraction is one of the biggest must-haves holding this thing up. They want a nice way to bind contexts to an entry in the pipe. Ironically the difficulty of figuring this out for JS is keeping pipes out of TS, but it wouldn't be that hard a problem in TS which has ways to treat `this` as special already. That, and the many competing proposals we already have. I'm fine doing an incremental rollout that doesn't need the placeholder `?` right now.