-
Notifications
You must be signed in to change notification settings - Fork 19
Remove jwt-decode as a peerDependency #45
Comments
Another option would be to make it as a dependency (I looked and it is not that big), ship the package as ES2015 modules and let clients deal with not being bundle by simple tree-shaking. |
Yep! That is even better... mono repo the shit out of these hocs so that they are published individually. |
as an example https://github.com/deepsweet/hocs |
Fantastic! Should we make this happen? |
Does Sagui support it as well as multiple builds?
|
But with lerna, it would be basically multiple packages, each with their own But given these are just libraries, we can also just use Babel and Jest directly. We don't need the webpack for anything anyway. |
Well, React itself and many ecosystem packages transpiles to
|
Actually the right name for this folder is |
Gotcha, we can do that as well. |
Either way, the monorepo solution sounds like a "major" endeavor, and I need the I'll prepare a first PR that simply adds it as an official dependency, and we can do the monorepo as a propper long term fix latter. Sound good? |
Good. |
Most people consume this library from their main entry point (`index.js`) which will make them require `jwd-decode` as a dependency. Move it to a explicit dependency for the time being since its footprint is really small. The long term solution is to break this since package into multiple individual packages, each containing their own HOC. #45 (comment)
Most people consume this library from their main entry point (`index.js`) which will make them require `jwt-decode` as a dependency. Move it to a explicit dependency for the time being since its footprint is really small. The long term solution is to break this since package into multiple individual packages, each containing their own HOC. #45 (comment)
Let’s do it! 🐒repo! (🐒 is "mono" in Spanish) |
btw, https://github.com/hocs is not taken... kinda like... it is wanting for a org to rise on it! |
I registered it and then deleted 2 days ago :) Decided that mono repo should be really mono. |
But it can be a the mono repo of the org! |
Imagine that, we can have an org with a mono repo that repos all the monos! |
and there will be only one repo called |
exactly |
We should extract the component that uses it on its own package.
Wdyt @deepsweet @xaviervia ?
The text was updated successfully, but these errors were encountered: