Webpack workaround no longer working from 1.4.6

[robmaas]

Webpack workaround no longer working from 1.4.6

[remarkablemark]

Thanks for opening this issue @robmaas! Do you have a suggestion on what the fix would be?

[robmaas]

@remarkablemark not really, I'm not very familiar with ES exports etc.
I'll try to take a look at it in the next couple of days, bit I'm a bit busy so might take a while.
Since nobody reported this earlier I don't think a lot of people encounter this issue so might not have the highest priority.

[remarkablemark]

@robmaas Thanks for the update! I'll also try to see if I can reproduce this locally in my spare time.

[MaxTwentythree]

I encountered a Probably similar issue:
"Cannot read properties of undefined (reading 'default')"
I had to downgrade from version 4.2.5 to 4.2.1 (npm) for it to work again

[robmaas]

@MaxTwentythree That's probably an unrelated other issue. My original problem also occurs on 4.2.1 with the same error I described earlier. It's not the same error you're encountering.

[robmaas]

@MaxTwentythree Sorry for the delayed response, been very busy lately.
Will try to take a look at it soon, or ask one of my colleague's to do so.

[remarkablemark]

All good @robmaas, thanks for the update

[MaxTwentythree]

@robmaas: same :)
Should I open a new issue with the problem I'm encountering?

[remarkablemark]

@MaxTwentythree can you provide a reproducible example?

[robmaas]

Hi @remarkablemark, the issue is definitely related the exports config introduced in #434

When removing the exports config from package.json the warnings dissapear even in 5.0.11 (which has a more advanced exports config).
I'm not very familiar with webpack and module exports etc. so it's a bit hard for me to understand what is really going on here.

I think this is somewhat related, because we do use moduleResolution: node.

[remarkablemark]

@robmaas Thanks for the update. Unfortunately, I can't remove exports from package.json since it will break ESM support. I wonder if there's something that can be done on Webpack side.