-
Notifications
You must be signed in to change notification settings - Fork 322
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
[Feature] Consider/ Requesting Access to read-only AST of Javascript Parser #717
Comments
@bnoordhuis adding to this, it seems like/ behaviour none of the I am seeing
|
This not the right issue tracker, please use https://v8.dev/bug to file new bugs. |
What is the problem this feature will solve?
Has the Access AST of the javascript module proposal been accepted into tc9 and node.js? Can someone take lead and help raise an proposal for this?
Can you make the AST available as read-only to developers in browsers [rethink security concerns] and js server environments if not on browers? Seems like the mozilla docs Parser_API documentation is somehow removed and I am still wondering how to access the file's parsed, even if read-only, AST
I wish to strongly vote for it, if this is in consideration. I recommend the access using a separate 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?
Access AST of the javascript module in runtime engines if not on browsers.
What alternatives have you considered?
The text was updated successfully, but these errors were encountered: