-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Proposal status: Access AST of the javascript module #45158
Comments
I think you misunderstand https://github.com/babel/babel/blob/main/packages/babel-parser/ast/spec.md - it's not a TC39 proposal, it talks about TC39 proposals. To answer your question: there are no plans to expose a JS parser in node. Apropos TC39 proposals: once a proposal is accepted, engines start implementing it. Once V8 implements it, it automatically makes its way into node. I'll go ahead and close this because there's nothing to do on our end but I can convert it to a discussion if you have follow-up questions. |
@bnoordhuis Can I make a TC39 proposal also? |
See https://tc39.es/ - yes, if you're a member; sort of, if you're not. |
:) i am in a strong belief that exposing the ast may be beneficial for many other purposes. it is available in python ast
|
@bnoordhuis I need help to file a TC39. Would you be open to spend a few minutes here to discuss raising the request? |
I'm not involved with TC39 (and don't plan to, either.) |
@bnoordhuis anyone you recommend me to raise this and help me with this. Do you think considering this for global function and I believe it is a good thought? I do think so. However, this is a risk; but present in python for access. Serious advanced options. |
I don't have any suggestions, I'm afraid. That said, I strongly suspect a proposal would get rejected, the reasoning being: libraries like acorn and esprima exist so why build that functionality into JS engines? |
@bnoordhuis |
+1 Reopening this feature request: #50949 |
+1 Reopening this feature request: v8/v8.dev#717 |
@bnoordhuis adding to this, it seems like/ behaviour none of the I am seeing
|
What is the problem this feature will solve?
Has the
Access AST of the javascript module
proposal been accepted into tc9 and node.js?I wish to strongly vote for it, if this is in consideration. I recommend the access using a seperate nodejs module api, if requested for my view. pls consider security and runtime risks based on your immense experience with such an nodejs module api access without a
commandline's force access ast option enabled
or other secure alternatives.What is the feature you are proposing to solve the problem?
What alternatives have you considered?
Using a bundler parser like ESTree, Typescript, and Babel. https://stackoverflow.com/questions/16127985/what-is-javascript-ast-how-to-play-with-it
Seems like a proposal was made to tc9 by babel.
[babel](https://github.com/babel/babel/blob/main/packages/babel-parser/ast/spec.md) - supports language features which is have not yet become a standard, but have a [proposal](https://github.com/tc39/proposals).
in this answer https://stackoverflow.com/a/66194129/3204942The text was updated successfully, but these errors were encountered: