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
Better parser error when using jsx #11499
Comments
This bug needs different steps in order to be fixed, but they can be done in the same PR.
If it is the first time that you contribute to Babel, follow these steps: (you need to have
|
I would like to take this up. |
@karansapolia it's yours! let us know (here or on slack) if you have any questions! |
@karansapolia friendly ping, are you still working on this? no worries if not! |
@existentialism so sorry, I have not been able to work on this yet. In case someone wants to pick this up, please feel free. I really want to start helping out with Babel, will try to chip in where I can next 🙂 |
@karansapolia no need to apologize at all! |
i want to try this. |
Awesome! Please feel free to reach out if you have any questions. |
Is this still available to pickup ? (: |
There is a PR opened for this: #11629 (@HiMrHu I noticed that you haven't responded, to my review: are you still working on it?) |
I don't have time to resolve this, I'm busy with my new job,just take it . I am sorry for this PR.------------------ 原始邮件 ------------------
发件人: "Jorge&nbsp;Henriquez"<notifications@github.com>
发送时间: 2020年6月16日(星期二) 凌晨1:47
收件人: "babel/babel"<babel@noreply.github.com>;
抄送: "MrHu"<454053152@qq.com>;"Assign"<assign@noreply.github.com>;
主题: Re: [babel/babel] Better parser error when using jsx (#11499)
|
No problem, thanks for telling us! |
Hello! Can I pick this issue up? |
We are working on this at #11722 with @penguingovernor. I'm looking for another issue you could help with. |
Please let me know that issue! I am so excited! I will try to help as much as I can! |
* Add "<" parser tests * No {jsx,flow,typescript} plugin * Type parameter * Valid JS Code * Add: better parser error when using jsx Address #11499 * Add: babel parser test Test parser with no plugins and when jsx is given with a js expression * Add: no flow but with typescript test * Add: type paramter test with no plugins (no flow) * Add: unclosed jsx element test
Was checking #11478 and testing out syntax and noticed we don't error with the normal "use this plugin/preset" like we do for proposals with JSX itself. @nicolo-ribaudo mentioned it's probably since jsx is implemented as a normal plugin so we didn't have
this.expectPlugin("recordAndTuple");
The text was updated successfully, but these errors were encountered: