Headless Chrome fails on new Chrome update 58.0.3029.81 - wrong launcher path (MAC)

I had the launcher working for HeadlessChrome until the latest google update 58.0.3029.81 and I can see is because the path for the launcher is now incorrect.

karma.conf:

    browsers: ['HeadlessChrome'],

    customLaunchers: {
      HeadlessChrome: {
        base: 'Chrome',
        flags: ['--headless', '--disable-gpu', ' --remote-debugging-port=9222']
      }
    },

When trying to launch Chrome, the launcher tries to find the resources.pak inside the wrong folder (/Applications/Google Chrome.app/Contents/Versions/58.0.3029.81/Google Chrome Framework.framework/Versions/A/resources.pak).

I believe it must have changed with the update as is now located inside /Applications/Google Chrome.app/Contents/Versions/58.0.3029.81/Google Chrome Framework.framework/Versions/A/Resources/resources.pak

02 05 2017 14:36:42.952:INFO [launcher]: Trying to start Chrome again (2/2).
02 05 2017 14:36:43.113:ERROR [launcher]: Cannot start Chrome
[0502/143643.028018:ERROR:resource_bundle.cc(767)] Failed to load /Applications/Google Chrome.app/Contents/Versions/58.0.3029.81/Google Chrome Framework.framework/Versions/A/resources.pak
Some features may not be available.

I have only tested this with macOS Sierra 10.12.4, not sure about windows.

[dpogue]

Well, the flag exists, but you’ll run into that resources.pkg error. It is only officially supported in Chrome 59 and up.

[missbruni]

For now I moved the resources.pak back to the launcher path to make it work again.