Package size engines & dependency on the react-dom

[GantMan]

When checking package size on bundlephobia I get the following error.

I also get an error when I try using the package-size module from npm

I understand this is probably dude to React Native, so you could consider setting an optional dependency? I'm not sure if that will work.

[mweststrate]

react-dom is not a (peer) dependency because it is only a dependency when using it in a DOM project, but not when using RN, etc.

If bundlephobia tries to resolve react-dom, it sounds like it is picking the wrong entry in the module in the first place, as the RN version doesn't require('react-dom'). Probably it doesn't respect this field in the package header? "react-native": "native.js",

[urugator]

@mweststrate Imho, since the depedencies are defined in package.json for the package as a whole and not for indididual compilation targets (entries), then ALL possible dependencies (for all compilation targets) should be stated in package.json.
If the dependency is used only sometimes, I think it makes sense to include such depedency in optionalDependencies field as suggested, even though it probably doesn't meet the definition of optional dependency (as missing dep may fail the build based on env)
The proper way would probably be to split the package?

[mweststrate]

Closing for now, multiple packages would be neat, but the problem doesn't seem urgent enough to invest in it now.