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.

Sign up for GitHub

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

Jump to bottom

Plugin API #1168

Closed
markelog opened this issue Apr 29, 2015 · 3 comments
Closed

Plugin API #1168

markelog opened this issue Apr 29, 2015 · 3 comments

Comments

@markelog
Copy link
Member

Description will be added later
@michaelficarra
Copy link
Contributor

Basic idea: allow sub-parsing functions to be overridden.

@markelog markelog mentioned this issue May 8, 2015
Closed
@ariya
Copy link
Contributor

ariya commented Feb 23, 2016

I'd like to close this for now and probably revisit it again in the future.

I believe that the most optimal approach to come up with a proper plugin API is by implementing various syntax extensions (see e.g. JSX support in #1467) and then abstracting it properly. This is more pragmatic than defining the plugin interface ahead of time and potentially struggling to use the interface properly.

@ariya ariya closed this as completed Feb 23, 2016
@ghost
Copy link

ghost commented Nov 20, 2017

@ariya What is the plan for such an API? I noticed people choose Acorn over Esprima because of lack of this option? There doesn't exist many Acorn plugins, but they exist.

And also Babylon have a plugin API. I know Babylon API seem to be for internal usage. Not sure there.
As far as I know Cherow also have a plugin API. A parameterized plugin system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ariya @michaelficarra @markelog