Create high level test(s) around tree shaking
As I understand it, the root need for !123 (merged) was to reduce the size of the module when used on a website and also to make sure it doesn't import something that will cause errors on a website. Whatever the high level need was, it would be good if a test can be made that covers it. For example if it is size, then maybe a test that loads up common components for a webapp and confirms that the size is less than x kB.