Config: Testing for Windows doesn't work when using a Linux subsystem

I am compiling with webpack in the Ubuntu subsystem of Windows. This is my generated erb-loader config:

module.exports = {
  test: /\.erb$/,
  enforce: 'pre',
  exclude: /node_modules/,
  use: [{
    loader: 'rails-erb-loader',
    options: {
      runner: (/^win/.test(process.platform) ? 'ruby ' : '') + 'bin/rails runner'
    }
  }]
}

The problem is here: runner: (/^win/.test(process.platform) ? 'ruby ' : '') + 'bin/rails runner'. While this works in Windows, it does not in the subsystem as it does not recognize it as Windows.

Replacing the runner option with runner: 'ruby bin/rails runner' solves the problem locally but breaks production on a linux server.

Is there a way I can distinguish development from production?

[rhys-vdw]

Just to be clear - rails-erb-loader does nothing smart with the runner command at present. Since the loader doesn’t require rails (can use ruby directly) I don’t think there’s a way to generalize.

Perhaps a solution like this makes sense:

module.exports = {
  test: /\.erb$/,
  enforce: 'pre',
  exclude: /node_modules/,
  use: [{
    loader: 'rails-erb-loader',
    options: {
      // Set this in each environment.
      runner: process.env.RAILS_ERB_LOADER_RUNNER,
    }
  }]
}

Just for my curiosity: Why is it that bin/rails runner fails in the Linux subsystem? Is it not executable?

[rhys-vdw]

Hey @jonhue if you do find a nice solution you’re invited to tackle #52. It wont make a difference in the case of webpacker though since it’s overriding the defaults. Perhaps if #52 is closed the webpacker default runner could be set to undefined so it just takes the default from this project.