graphiql-rails rubygem vs graphiql node module
The general trend so far has been moving away from wrapper gems via sprockets and use node modules with webpack instead. I see graphiql-rails gem in gitlab 11 as a deviation. Any rationale for this choice? Can we consider using the node module directly?
This will help the debian packaging in the short term as we try to package all rubygems natively and install node modules directly via npm (this is a temporary step until we have all node modules packaged natively as well).