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.

This loader is not working with absolute paths.

See original GitHub issue

Bug description

I try to use this loader in scope of WebPack configuration right now, but as fact that I have a very big project and around all files we are using absolute paths, when I try to make a build a get more than 359 errors related to the path. I can’t find the ability to add some configuration or additional plugin. But the way to update each file is a little bit crazy for me. )

Reproduction

Use absolute files in your project

Node.js package manager

yarn

Environment

Node: v14.17.0
NPM: 8.6.0
Webpack: 5.62.1

Can you contribute a fix?

I’m interested in opening a pull request for this issue.

Issue Analytics

State:
Created a year ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

maksym-nezhurincommented, Aug 12, 2022

Yeah, I also think so. But it was working before I replaced the loader (from babel to esbuild). There is my configuration of 3 main files that is responsible for bundling. Maybe, I have to add some additional plugin or replace ‘module-resolver’ that is responsible for the path (as I understand).

0reactions

maksym-nezhurincommented, Aug 12, 2022

Okay! Thank you!