-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Not work with opal 1.2.0 and opal-sprockets 1.01 (it use sprockets 4) #49
Comments
I encountered the same problem The current inesita template seems not to work well with latest sprockets, and if you revert to an old sprocket version you lose the possibility to use latest Opal version. I've rewritten the on-site sample app by removing sprocket, and use instead a rake based approach to build everything You can try it here : https://github.com/jugcoding/raked-inesita My alternative rake builder is here : https://github.com/jugcoding/opal-rake Compilation becomes instant with rake. |
Hi, your fork works for me, though, you need update .ruby-version, because 2.3.1 is too old. not works anymore. |
@jugcoding , BTW, after update to newest opal and opal-sprockets, still get same error if not use opal-rake. current, opal-sprockets project is live maintained, could you please port some of your's fix to upstream? |
It's the first time I wrote a Gem. So I forked opal-sprockets. But opal-rake is not related to sprockets, it's a completely different build system. Unfortunately, there is nothing to port upstream. Are you sure you need sprockets? You can do the same things with opal-rake What sprockets functionality is missing for you in opal-rake ? I don't know what is the purpose of this .ruby-version: may the best approach is to remove it from the repo ? |
What i means is inesita depend on opal-sprockets, anyway, i will try opal-rake later. thank you.
Yes, you can remove it, or, you should specify a ruby version which can working with your's gem. |
Following is a my forked version playground.
It works if use old original Gemfile.lock, but when i try to update to use newest opal-sprockets, it failed.
Following is back trace.
The text was updated successfully, but these errors were encountered: