[Still Work in Progress] Separating into loader and react-binder

[piglovesyou]

Ref. #159

• Use Lerna

• Share lint logic
• Share test logic
• Share build logic
• Share *rc file as much as possible

[piglovesyou]

I'm waiting for reply from @frenzzy before going forward.
#159 (comment)

[frenzzy]

Do you have an idea how to name a package with react components?
Oh lerna.. looks more complicated than how it is now.
Looks like isomorphic-style is taken and already does what we want.

---

I am waiting for [IN PROGRESS] CSS AS FIRST-CLASS CITIZEN in webpack which could be a game changer and make this package unnecessary.

Another question is why css-loader does not have an option to exclude runtime code from the bundle - this feature may help with rendering styles on both client and server-side too.

Also would be nice to do a research about other ways to extract critical path css with less overhead - for example without runtime code and with faster compilation, maybe even consider alternatives like css-in-js solutions.

I am still not sure about the future of isomorphic-style-loader and maybe it is better to leave it as is for now... 🤷‍♂️

[piglovesyou]

@frenzzy I see, I understood you had more thoughts than last time you commented. I agree with you that separating loader and react-binding is definitely not emergency.

I'll close this.