Closed clintwood closed 5 years ago
Project appears to be dead.
@alexschrod Is there an alternative to this, I'm not aware of one?
I switched to using Babel with babel-preset-flow
and haven't run into
issues with that one yet. https://flow.org/en/docs/tools/babel/
Psst: If using npm at least, use @babel/preset-flow
instead
of babel-preset-flow
.
On Tue, 13 Nov 2018, 13:05 Clinton Wood, notifications@github.com wrote:
@alexschrod https://github.com/alexschrod Is there an alternative to this, I'm not aware of one?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/flowtype/flow-remove-types/issues/65#issuecomment-438243043, or mute the thread https://github.com/notifications/unsubscribe-auth/AAu2Avn6Ry-CbL2tV6B3BT-g9koZra_0ks5uurWCgaJpZM4T0eVD .
@alexschrod, Thanks!
I've been working on a project called Sucrase with similar goals, and it's pretty stable at this point: https://github.com/alangpierce/sucrase . It transforms Flow, TypeScript, JSX, and imports, and it looks like it's probably faster than flow-remove-types.
@alangpierce, Surcrase looks great! Will give it a try. Interestingly you've hit my requirement 100% - Transform non-standard extensions of modern JS to just modern JS - FAST. Nice!
Hey everyone, I'd like to apologise for the radio silence. I'm working on a v2 release that will upgrade the parser, stay in sync with the main Flow repo and address the outstanding bugs.
FWIW I think the lightweight approach that this package takes is still one of the best ways to strip Flow types - if that's truly all you need. Stripping types using the Babel preset might indeed be the way to go if you're already using Babel for other things.
I've switched to Typescript so you are welcome to close this issue. Thanks.
@motiz88 i know you're probably doing this in your freetime, so thanks for working on it at all :)
still need to ask, tho: any updates soon? really don't wanna introduce the whole babel toolchain just for stripping flow types but it's becoming a serious impediment for us at this stage
@chapati23 I have the pieces all lined up - some urgent work on another project took precedence, hence the delay, but v2 is still coming very soon. I'll share a timeline when I can definitely commit to it.
We've just published v2.99.0 of both flow-remove-types
and flow-node
. Future releases will be aligned with Flow releases (e.g. v2.99.0 ↔ Flow 0.99.0) and will always use the latest version of the Flow parser for maximum compatibility.
The code has now moved to the main Flow repo, and this separate repo will be archived soon; please use the Flow issue tracker for any further discussion.
Thanks for the update @motiz88, great to hear!
@leebyron, I see last release was back in Oct 18, 2017.
If accepted I'd be keen to make use of
--copy-source
feature submitted in PR #64