Note that for some reason, after I migrated my @hydroperx/metro package from using main to exports in the NPM manifest, Webpack simply doesn't take the exports of the package, so we're getting a different error now, but the above React error insisted until then.

There is no problem here who is better - vite or webpack, there is a problem with your library, webpack is simply stricter here, as it allows you to catch problems at the bundling stage, while white is less demanding, but this does not eliminate the problem that other tools and other assemblers will not work with your library in the same way, the behavior of webpack completely follows the Node.js/deno/bug behavior.

What's the problem?

You *can't using import and reexport without extensions, this is literally mandatory to use for ES modules.

https://nodejs.org/api/esm.html#import-specifiers

Relative specifiers like './startup.js' or '../config.mjs'. They refer to a path relative to the location of the importing file. The file extension is always necessary for these.

https://docs.deno.com/runtime/fundamentals/modules/

With ECMAScript modules, local import specifiers must always include the full file extension. It cannot be omitted.

Using your library can be broken for other developers.

You have "type": "module", it means your library is fully compatibility with ES modules.

@alexander-akait I've deleted the SO question, but here's the Reddit post detailing everything: https://www.reddit.com/r/learnjavascript/comments/1k4neum/invalid_hook_call_in_react_using_webpack/

I recommend do not study how import/export works from how vite/webpack/ets handle, they can be less strict in some areas and use official documentation to understand the work - MDN, Node.js, tc39 official proposals.

@hydroperx Do you still have a problem with webpack?

@alexander-akait Right now, it'd be first this "new" exports issue that you've responded to, and then this misleading React hook error as I've given full information in the above Reddit post.

I've to give it a try to fix that exports issue, but I'd have to update my react library for that :/

When I said exports I refer to the exports field in package.json, not the export statement. @alexander-akait

I've to give it a try to fix that exports issue, but I'd have to update my react library for that :/

I don't think you need to do it

Uncaught TypeError: Cannot read properties of null (reading 'useContext')

It means you have two different copies of react, check your dependencies, maybe you can accidentally install another version somewhere

We respect the exports field in package.json, and respect was added a long time ago