Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

typescript, tsx, jsx support #14

Open
4 tasks
reggi opened this issue Dec 21, 2018 · 3 comments
Open
4 tasks

typescript, tsx, jsx support #14

reggi opened this issue Dec 21, 2018 · 3 comments

Comments

@reggi
Copy link
Owner

reggi commented Dec 21, 2018

Syntax block support for

  • jsx support
  • typescript support
  • tsx support
  • babel support

How about we pipe these code blocks to another Unix command?

Add flag array to command.

Example,

--type=ts --type=typescript

Then we can pass all the code blocks in chunks into the ts-node command.

Kinda wanna support bash and go and rust blocks.

@reggi
Copy link
Owner Author

reggi commented Dec 21, 2018

@ljharb thoughts?

@ljharb
Copy link
Collaborator

ljharb commented Dec 21, 2018

If it won’t require any extra work from evalmd consumers, then sure, that seems fine. I’d prioritize js and jsx to start tho.

@reggi reggi changed the title Proposal for rewrite. typescript, tsx, jsx support Aug 31, 2019
@ljharb
Copy link
Collaborator

ljharb commented Oct 14, 2024

In general, I think that probably #27 would be better - iow, just use eslint's config, which will/can include the ability to define a parser that can handle whatever the user likes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants