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
Description
Shipping eui components as scoped packages.
Right now the eui ships as a single unit which has a huge surface area of 45.5MB, as per NPM.
Say someone wants to just consume the button component, but he's been shipped with table components as well. Though he can use tree shaking to remove unused code, this depends on the user's configuration. This would also help eui to be served over cdn, where we can ask for individual components on demand by adding script tags.
This would also allow to colocate any bugs into individual components, which can be fixed and released independently.
The idea is to break the entire codebase into smaller packages, possibly lerna packages which can colocate in the same mono-repo and published individually.
Description
Shipping
eui
components as scoped packages.Right now the

eui
ships as a single unit which has a huge surface area of45.5MB
, as per NPM.Say someone wants to just consume the button component, but he's been shipped with table components as well. Though he can use tree shaking to remove unused code, this depends on the user's configuration. This would also help eui to be served over cdn, where we can ask for individual components on demand by adding script tags.
This would also allow to colocate any bugs into individual components, which can be fixed and released independently.
The idea is to break the entire codebase into smaller packages, possibly lerna packages which can colocate in the same mono-repo and published individually.
Dividing the dependency into scoped packages will make it more reasonable and feasible.
Would love to discuss 📢
The text was updated successfully, but these errors were encountered: