Configuration option loader(s) is ignored

[karrikuivanen]

Hi,

in the same vein as #23, unless I'm mistaken, it seems that the --loader esbuild option is not currently supported.

Similarly to the externals issue, a merge of user provided loaders with the default stack could be considered.

My use case is testing modules that use static binary assets.

My esbuild-runner-config.js:

module.exports = {
  type: 'bundle',
  esbuild: {
    target: 'node14',
    format: 'cjs',
    loader: {
      '.png': 'binary'
    }
  }
}

Result:

 > lib/loader-issue.js:1:16: error: No loader is configured for ".png" files: assets/img/image.png
    1 │ import pngImage from '../assets/img/image.png'
      ╵                      ~~~~~~~~~~~~~~~~~~~~~~~~~

Thanks for a great tool!

[gustavoschmidt]

loaderS :)

[folke]

I just added support for custom loaders. @gustavoschmidt the option is loader without the s ;)

platform was another option that was overshadowed by esbuild-runner. Also fixed.

Let me know if you have any more issues with this.

Thank you for reporting!