Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Configuration option loader is ignored when type: "transform"

See original GitHub issue

Hi,

I noticed having type: 'bundle' in my esbuild-runner config broke my test coverage, so swapped it out to "transform".

This, however, caused my loader definition to be ignored.

Would it be possible to give type: 'transform' the same love you gave to bundle in #24 ?

Thanks!

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:10 (4 by maintainers)

Top GitHub Comments

1reaction

zemlanincommented, Feb 6, 2022

Hi. Is fix still coming?

1reaction

marcelbeumercommented, Jun 14, 2021

Right, I know what’s happening here. I’ll work on a fix!

Messages crossed. Thanks!

Top Results From Across the Web

Configuration option loader(s) is ignored · Issue #24 - GitHub

My use case is testing modules that use static binary assets. My esbuild-runner-config.js : module.exports = { ...

asp.net - Web Config Transform not working - Stack Overflow

It describes how to modify the .msproj file to overwrite the current web.config by the transformed version. I will first describe that workaround...

Options - Babel

If any of patterns match, the current configuration object is considered inactive and is ignored during config processing. This option is most useful...

API - esbuild

This setting is a convention from Webpack that esbuild respects for any imported file, not just files used with inject. #Loader. Supported by:...

Configuration - React Styleguidist

js file in your project's root folder. You can change the location of the config file using --config CLI option. assetsDir #. Type:...