Support useStyles(style) for Hooks

[piglovesyou]

Fixes #154.

I'm glad if you take a look this, @frenzzy .

[codecov-io]

Codecov Report

Merging #159 into master will increase coverage by 0.18%.
The diff coverage is 81.81%.

@@            Coverage Diff             @@
##           master     #159      +/-   ##
==========================================
+ Coverage   80.76%   80.95%   +0.18%     
==========================================
  Files           3        4       +1     
  Lines          52       63      +11     
  Branches       12       15       +3     
==========================================
+ Hits           42       51       +9     
- Misses          9       11       +2     
  Partials        1        1

Impacted Files	Coverage Δ
src/useStyles.js	81.81% <81.81%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bd5af84...cc21210. Read the comment docs.

[piglovesyou]

Glad if you take a look at this, @frenzzy .

[frenzzy]

I think all react-related stuff should be moved away from isomorphic-style-loader package.
Since webpack loaders usually are dev-dependencies but react HOC/hook must be a dependency.
See also #156

[piglovesyou]

@frenzzy Thank you for the information, that's a good discussion. Yes, I'll follow decision the issue will make. Or, we can move withStyles and useStyles together later, since useStyles is just another implementation of withStyles.

[piglovesyou]

@frenzzy Do you have a plan to separate the package into a loader and a react binding? That would be a breaking change. Would you like me to create the PR?

[frenzzy]

Or, we can move withStyles and useStyles together later, since useStyles is just another implementation of withStyles.

Agreed. Let's do this, I will release it as v5.1.0 today.

Do you have a plan to separate the package into a loader and a react binding? That would be a breaking change. Would you like me to create the PR?

It would be nice to split them, but I don't have time to do it. Need to create another repo for react bindings, configure builds, write tests etc. After that make a PR to isomorphic-style-loader with removed react stuff and special docs. Breaking change is not a problem I believe, we will just increase version number to v6. Help is really appreciated here, I even consider adding a new maintainers to this repo.

[frenzzy]

Released as v5.1.0 🎉

[piglovesyou]

Thank you frenzzy. Yeah, that is going to be some work. I see, you're thinking another GitHub repo for it. I think I'll give it a try in the next free weekends.

[piglovesyou]

@frenzzy Instead of separating the repo, what would you say if we about monorepo with Lerna?

Pros

• Documenting in one place (root README.md) - Easy to read and easy to maintain
• Easy to track for each packages' change for maintainers - Lerna has a functionality to link to each other
• Possibly we can provide Vue.js binding as third package in the monorepo

Cons

• Increase complication of codebase a bit - But this is inevitable when we separate it anyway
• I'm still not sure Lerna is the right choice (Only two packages. Should it be worth for us?)

[piglovesyou]

We finished this talk on #160 (comment)