There are still cases where ember-cli-rails reports the build as unsuccessful even though there were merely warnings not actual errors.
e.g.:
Warning: ignoring input sourcemap for vendor/ember/ember.debug.js because ENOENT: no such file or directory, open '/Users/tony/src/ember_rails_test/frontend/tmp/source_map_concat-input_base_path-SS0N4DR8.tmp/vendor/ember/ember.debug.map'
I was wondering if there is a reason this approach was taken, and if its possible to rely on something like the exit code status of ember cli building the project instead? Is the exit code status not reliable either?
Which operating system and version is the project developed on?
mac os sierra 10.12.4
Which version of ruby is the project developed on?
ruby 2.4.1
Which version of npm is the project developed on?
npm 5.3.0, but using yarn 0.27.5
Which version of ember-cli is the project developed on?
2.14.2
There are still cases where ember-cli-rails reports the build as unsuccessful even though there were merely warnings not actual errors.
e.g.:
Lines that start with Warning are not accounted for and rejected in
build_errors: https://github.com/thoughtbot/ember-cli-rails/blob/master/lib/ember_cli/build_monitor.rb#L42I was wondering if there is a reason this approach was taken, and if its possible to rely on something like the exit code status of ember cli building the project instead? Is the exit code status not reliable either?
Which operating system and version is the project developed on? mac os sierra 10.12.4
Which version of
rubyis the project developed on? ruby 2.4.1Which version of
npmis the project developed on? npm 5.3.0, but using yarn 0.27.5Which version of
ember-cliis the project developed on? 2.14.2What is the
railsversion? 5.1.3What is the
ember-cli-railsversion (fromGemfile)? 0.9.0What is the
ember-cli-rails-addonversion (frompackage.json)? 0.8.0Is your application server multi-threaded (such as
pumaandunicorn) or is it multi-process (such as thin and webrick)? using pumaWhat are the contents of
config/initializers/ember.rb?