[DRE-maint] Bug#1013499: ruby-hamlit: FTBFS: ERROR: Test "ruby3.0" failed. Exiting.
Pirate Praveen
praveen at onenetbeyond.org
Thu Aug 18 23:28:13 BST 2022
On Fri, 19 Aug 2022 00:54:07 +0530 Pirate Praveen
<praveen at onenetbeyond.org> wrote:
> On Fri, 24 Jun 2022 09:07:48 +0200 Lucas Nussbaum <lucas at debian.org>
> wrote:
> > > SyntaxError: Unexpected token 'export'
> > > at Object.compileFunction (node:vm:352:18)
> > > at wrapSafe (node:internal/modules/cjs/loader:1033:15)
> > > at Module._compile
(node:internal/modules/cjs/loader:1069:27)
> > > at Object.Module._extensions..js
> (node:internal/modules/cjs/loader:1159:10)
> > > at Module.load (node:internal/modules/cjs/loader:981:32)
> > > at Function.Module._load
> (node:internal/modules/cjs/loader:822:12)
> > > at Function.executeUserEntryPoint [as runMain]
> (node:internal/modules/run_main:77:12)
> > > at node:internal/main/run_main_module:17:47
>
> This looks to be caused by coffeescript 2 transition. coffeescript 2
> now produce ES6 by default which execjs cannot handle yet.
>
>
https://stackoverflow.com/questions/46484433/coffescript-2-output-es6-code-using-webpack-and-coffee-loader-will-it-automati#46986570
>
> I am not sure what is the ideal fix here.
>
>
https://stackoverflow.com/questions/51379326/current-execjs-runtime-doest-support-es6#51382180
> suggest setting ENV['EXECJS_RUNTIME'] = 'Node' but I think we already
> use nodejs.
coffee-script gem is deprecated, may be we can ask upstream not to use
coffee-script gem and for now disable this test.
https://github.com/rails/ruby-coffee-script/issues/22
More information about the Pkg-ruby-extras-maintainers
mailing list