You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As perry grows, it will eventually get more and more bloated.
And even though some users can actually just add perry with everything on it and enable/disable features, they should also be able to choose whether they want to actually load those extra modules or not.
This issue aims to track the discussion and development of modular architectures for Perry's features.
Firebase for example offers a single way of using it all, and a more pluggable way where you can actually import the core of it and other modules as you need (e.g.: you can import only the auth module if you're not using the database at all)
This was a bit addressed lately by the #60 PR that was recently merged. Now Perry lazy loads extra features to load them only when you actually use them.
Even though, they might end up in your final webpack bundle so your webserver can serve them, unless you're using the <script> tag approach.
As perry grows, it will eventually get more and more bloated.
And even though some users can actually just add perry with everything on it and enable/disable features, they should also be able to choose whether they want to actually load those extra modules or not.
This issue aims to track the discussion and development of modular architectures for Perry's features.
Firebase for example offers a single way of using it all, and a more pluggable way where you can actually import the
core
of it and other modules as you need (e.g.: you can import only theauth
module if you're not using thedatabase
at all)Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: