Don't explode if child process is already dead

[mikker]

My brunch watcher is always, always already dead at this point (why? Will we ever know?)

Fixes #5

Thanks!

[rstacruz]

Thanks for this! Would love to know what you think of npm-pipeline-rails and how you're using it.

[rstacruz]

1.6.1 is out with this fix, thanks!

[mikker]

Great! Glad to help. I'm using it with as many Rails projects as I can. Usually with brunch but I could definitely imagine doing it with Webpack too.

As you say so yourself, the asset pipeline is too old and cumbersome and the web has come far since it was made. Doing even the smallest amount of front-end – JavaScript OR CSS – without access to npm and node_modules gets tedious fast.

I think your lib here does the minimally required setting up to allow maximum customisability. Just as I'd want it to.

[mikker]

I sometimes did this along with a Webpack dev server script:

In the bottom of development.rb:

if defined?(Rails::Server)
  class WebpackDevServer
    def self.run!
      return @pid if @pid

      @pid = Process.spawn("./webpack.server.js")
      Signal.trap("EXIT") { Process.kill(9, pid) }

      @pid
    end
  end

  WebpackDevServer.run!
end

Which I suppose is a somewhat brutal way of doing what this gem is doing 😄