Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Remove deprecated options

See original GitHub issue

The --flow-parser and --parser postcss options are deprecated. Let’s remove them 🔥

Let’s also search for other deprecations in the code base and get rid of them too.

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:11 (11 by maintainers)

Top GitHub Comments

2reactions

thorn0commented, Jan 10, 2020

What exactly are we going to remove in 2.0? Only --flow-parser and --parser postcss? What about --parser babylon? Do we want to remove deprecated option values like true and false for proseWrap?

Is it necessary that getSupportInfo be able to return correct info about any previous versions including removed options? This means we can’t completely remove them, right? So what exactly should be done in this issue then?

1reaction

thorn0commented, Jan 28, 2020

The markdown parser is documented and not even deprecated. On the other hand, remark never was documented. That TODO seems to express just an intent to rename markdown → remark sometime. But if we really want to go that way, it should be done gradually like it’s been done with babylon → babel. I doubt we want to though. What for?