These are chat archives for opal/opal
webpack 'foo-bar'and does the equivilent webpack command to add foo-bar to the mix? Does that even make sense?
Opal::Builderis a compiling pipeline completely separated from sprockets
- Integrate Rails with NPM by default
Right now in Ruby-based apps is possible to manage asset dependencies adding assets gems to Gemfile:
In order to have this working people have created a lot of Ruby gems to wrap most popular JS libraries (thus the *-rails suffix) but doing this and having to maintain gems periodically everytime a new version of JS library is release is a busy work and we would like to have better solution for this.
NPM is not only the default package manager for Node.js, some full-stack frameworks like Laravel (PHP), Phoenix (Elixir), Play! (Scala) and some developments environments like Visual Studio (.NET), ember-cli (Ember.js) and angular-cli (AngularJS2) are using NPM for asset dependencies management and there are more than 250,000 packages published right now in NPM registry making it a great solution for assets management.
We want to integrate NPM with Rails by default, we understand that this could require adding Node.js as dependency for Rails development, we can investigate workarounds to avoid that (e.g creating a Ruby script reproducing the bare minimum required to do only "npm install").
"use strict"to generated code, please let me know if you know of any case it can lead to problems
warningat compile time and from
errorat runtime to hove an experience more similar to what we have in CRuby
Opal::Config.dynamic_require_severity = :ignore