You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd be happy to add an official opal/opal-webpack repo (with its official maintainer ), sprockets support has been extracted from opal@master to opal/opal-sprockets, paving the way exactly for this kind of things
I'd help out updating the documentation here and there, but lack the webpack insight to jump at the code. Nonetheless, webpack appears to be the future (given the challenges Sprockets is facing), so maybe it's time to push it a little more towards the spotlight. What do you think?
The text was updated successfully, but these errors were encountered:
On Apr 23, 2017 8:15 AM, "Sven Schwyn" ***@***.***> wrote:
This appears to be the most advanced shot at opal-webpack, how about
moving it to the Opal organization and start looking for a maintainer?
@elia <https://github.com/elia> write on Gitter (Oct 07 2016 22:27):
I'd be happy to add an official opal/opal-webpack repo (with its official
maintainer ), sprockets support has been extracted from ***@***.*** to
opal/opal-sprockets, paving the way exactly for this kind of things
I'd help out updating the documentation here and there, but lack the
webpack insight to jump at the code. Nonetheless, webpack appears to be the
future (given the challenges Sprockets is facing), so maybe it's time to
push it a little more towards the spotlight. What do you think?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#39>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AASIo5F1ApbD-TCWUBU4d9k8Y0QzJtu2ks5ry1z0gaJpZM4NFa5H>
.
This appears to be the most advanced shot at
opal-webpack
, how about moving it to the Opal organization and start looking for a maintainer?@elia write on Gitter (Oct 07 2016 22:27):
I'd help out updating the documentation here and there, but lack the webpack insight to jump at the code. Nonetheless, webpack appears to be the future (given the challenges Sprockets is facing), so maybe it's time to push it a little more towards the spotlight. What do you think?
The text was updated successfully, but these errors were encountered: