findDOMNode brings whole react-dom to the chunk

say you have code like this

import Loadable from "react-loadable";
const PhoneAsync = Loadable({
  loader: () => import("react-phone-number-input"),
  loading: () => <span>Loading the phone number</span>
});

this will produce a separate chunk (I’m talking about webpack2+, like c-r-a setup). This chunk will look like this

Same issue in https://github.com/catamphetamine/input-format

[stereobooster]

these are very trivial and simple things

I suppose you have extensive experience in implementing tree shaking and bundlers. I will not bother you with my comments anymore.

[stereobooster]

How are you going to use React in a web browser without react-dom?

Yes I will use it in my application. I’m saying component should not depend on it.

The only question is: why did your bundler include it the second time in this separate chunk because it must be in your main chunk already.

Because webpack cannot do magic. You asked for it it gets it for you. Tree shaking is very limited - you can use https://www.npmjs.com/package/eslint-plugin-tree-shaking to see what won’t be tree shaken.