Why Module Federation does not recognizes version of dual ESM+CJS packages?

[krutoo]

Hi, im trying to share @sentry/browser and in result I have warnings about it version:

This warning appeared after updating @sentry/browser - now this package is dual (esm + cjs)

[krutoo]

@ScriptedAlchemy Can you suggest solution?

It is major problem for us with dual ESM+CJS packages

These packages usually has three package.json file:

# root of the package
./package.json # main package with vestions and other meta info
./dist/esm/package.json # here is just { type: module }
./dist/cjs/package.json # here is just { type: commonjs }

[ScriptedAlchemy]

Just point it directly at what you want to share. Use the import key on the share object and just put the path to ESM if you want ESM. Or use a trailing slash on the package name. For example, "@sentry/browser/" then set the required version by importing the package.json and pass it the key for the package.

[krutoo]

@ScriptedAlchemy but i dont use this package directly in my project, it is a transitive dependency

Describing each transitive dependency in build config is a gigantic amount of work

[ScriptedAlchemy]

Then how do you share things currently? If sentry is shared then you must have listed it in shared

[krutoo]

@ScriptedAlchemy as I said earlier, I dont use it package directly in my codebase but i share exactly @sentry/browser because of a microfrontend reasons

[ScriptedAlchemy]

@ScriptedAlchemy as I said earlier, I dont use it package directly in my codebase but i share exactly @sentry/browser because of a microfrontend reasons

So change the share key?

Sentry/browser:{import:anythinkyouWant}

Or try a trailing slash on the object key

[ScriptedAlchemy]

Ahh this is about resolving upwards. How i workaround it is usually to require the package.json in a loop and resolve the version off it. There's a pr open for upward traversal but it's not merged and needs to be ported to rspack still