Maybe provide tree-shakeable alternative to preact/compat?

[danieldiekmeier]

I've read the release notes for 10.0.0-alpha.0 (https://github.com/developit/preact/releases/tag/10.0.0-alpha.0) where you say that

preact/compat […] still has both named and a default export to remain compatible with react

I absolutely get that, but some of the functions in compat can actually be useful on their own! Yesterday, I wanted to use memo, but it more than doubled my bundle size because now I was importing all of compat. (I then copied just memo into my codebase, but I don't think that's necessarily the best way to go about this. :D)

Do you think there may be value in providing some of the functions on their own? Maybe something like

import { memo } from 'preact/utils'

On first look, these functions could be especially useful on their own:

• Portal
• PureComponent
• memo

[JoviDeCroock]

Normally the module field should be tree-shakeable, so you imported it as import { x } from 'preact/compat' and you accept module field in your bundler config?

I'll give this a try tonight if this is the case, that shouldn't be the behavior imo

[danieldiekmeier]

I created a reproduction so it's easier to talk about: https://github.com/danieldiekmeier/preact-compat-treeshake-reproduction

This just uses the Webpack default settings!

[JoviDeCroock]

Can confirm, tinkered a bit with webpack aswell and adds more than needed (since it also adds hooks etc).

[robertknight]

Perhaps we could pull utilities like memo and Portal into a separate bundle which preact/compat just re-exports?

[developit]

Would marking the package.json with pure / sideEffects:false help here?

[JoviDeCroock]

@developit most of the polyfill code will still get injected though but yes that could shave something.

[vtenfys]

I've created PR #2006 to partially address this (see its description for details).

Another way this could be approached is to stop exporting a default object, and instead create a Babel plugin to transform import React from "react" into import * as React from "preact/compat", rather than encouraging people to use bundler-specific options - thoughts?

[vtenfys]

Also just curious - what's the context behind #1552 being closed?