-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Custom plugins in REPL. #1211
Comments
@DylanPiercey we agree! #858 Definitely something we'd love to do, but have been busy with other things. Would love help :P |
Ah thanks for the link. I was looking through and I don't think it'd be to bad. Perhaps I'll give a shot if I get some free time next week. |
Awesome, looking forward to it! |
@DylanPiercey the issue I had with unpkg is that we would need to require plugins to do a umd build type thing unless we also run webpack on the fly |
Yeah we can do that, just can get kinda big, but if it works we can try! |
I think it will make a lot more sense with babel 7 since we got rid of babel-runtime for deps, and we have the polyfill to the repl |
@hzoo I think the user would more/less expect it to take some time to fetch third party modules so I don't think it'd be too much of an issue. Also with wzrd they have a '/multi' api which we could use in this case to bundle all of the presets together. |
Oh ok cool! I'm not that knowledge about wzrd but that sounds great - I really want this feature! btw have you joined our slack? can talk in #website other sites that do this are https://runkit.com, https://github.com/christianalfoni/webpack-bin |
@hzoo could you point me to the place where the current presets are loaded? |
Messaged on slack, but https://github.com/babel/babel.github.io/blob/master/scripts/repl.js#L32, via babel-standalone |
I was just thinking it'd be pretty cool to extend the preset options to have a text input where you could put in whatever plugin you want (e.g.: babel-plugin-closure-elimination) and it would then try to download it from unpkg and enable it. To keep it simple it could just be a comma separated list of custom plugins.
This would make quickly trying a plugin trivial on the website.
The text was updated successfully, but these errors were encountered: