-
Notifications
You must be signed in to change notification settings - Fork 225
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
coffee-script is getting deprecated #384
Comments
Tilt doesn't depend on |
Thanks for the quick reply @jeremyevans ! I see you have been cautious in those tests, thanks for that. Maybe the Gemfile change you mentioned would be great. I also think we could let users know that those coffee-script related features are going to be deprecated, so they can move away from it without getting surprised. WDYT? |
I'm not sure if we'll be deprecating tilt's support for coffee-script. The tests still pass, so even if the coffee-script gem is no longer actively maintained, tilt's support is still usable. Tilt tends to be conservative in terms of deprecation, only deprecating support when it causes issues in CI. I'll submit a PR for the Gemfile change. |
I am afraid they don't pass with with Coffeescript 2.x, which was released in 2017:
Admittedly, I have tested with tilt-2.0.10, but checking the source code, the test cases were not updated yet. BTW the coffee script path can be modified via env variable: |
The specs pass in CI, which uses the latest version of the coffee-script gem, which appears to use CoffeeScript 1.12.2. FWIW, The spec failures you are seeing with CoffeeScript 2.x appear to be due to fragile tests, and not the underlying support being broken. We don't generally deprecate/remove support unless something is actually broken on modern Ruby or we cannot properly test it in CI. See #382 for the last time we deprecated template engines. Are you OK with the change proposed in #385? |
Just to explain the context, while this seems to be originally reported by Debian/Ubuntu folks, I'm coming with from Fedora. The issue is that the abandoned coffee-script-source gem prevents update of the Coffescript compiler. While Tilt users would likely preferred to use the most recent Coffeescript for all possible purposes, they won't be able to do that due to that gem. So this is catch 22. Coffeescript upstream would probably like everybody to use Coffeescript 2.x, users would probably like to use Coffeescript 2.x, Tilt probably supports Coffeescript 2.x, but nothing of this happens, because there is abandoned coffee-script-source gem which won't be ever updated. On Fedora, we could probably update the coffee-script-source gem to provide the Coffeescript 2.x, but in that case, we will face the failing test suite and the solution would be to ignore the test cases, i.e. to drop the coffee-script dependency. However, given that Rails does not use Coffeescript anymore (and I believe that is the reason behind abandoned coffee-script-source gem), the solution for Fedora will likely be dropping the coffee-script dependency from Tilt package and the test suite can ignore the test cases in such situation just fine. I'll also likely drop the entire coffee-script gem package from Fedora. Therefore it won't be issue for Fedora anymore, but still, this situation is unfortunate. And just FTR, I am certainly not blaming Tilt here.
Correct
That also seems to be correct. If the tests were adjusted to support CoffeeScript 2.x and they were also really tested against CoffeeScript 2.x, that would possibly make the situation less unfortunate.
This won't help, because we don't use Bundler to run tests on Fedora. Can't speak for others, though. |
I would guess it more likely that Tilt users would be using Coffeescript for legacy projects that used Coffeescript 1.x and have not yet migrated off of it, as opposed to active projects using Coffeescript 2.x with the enivronment variable to force the gem to load the external Coffeescript source.
I'm sure Coffeescript upstream would prefer that everyone use the latest release of Coffeescript. However, I doubt Tilt users care much about Coffeescript 2.x.
I would recommend against that approach.
That sounds like a better approach to me.
We would accept patches that allow the specs to pass with both CoffeeScript 1.x and 2.x. |
Update tilt.gemspec so it doesn't need to be regenerated via a rake task. Fixes #301, #380, #385, #393, #384, #390
tilt
right now is failing to build from source in Debian and Ubuntu because of an issue withcoffee-script
:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013504
coffee-script
seems to be on the deprecation route, the upstream maintainers are not willing to support it anymore:rails/ruby-coffee-script#22 (comment)
Due to that,
coffee-script
is going to be removed from Debian (and Ubuntu) soon:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019927
and this will impact
tilt
. Could we try to avoid the dependency oncoffee-script
?The text was updated successfully, but these errors were encountered: