As an ESL architect, I want to have a more flexible distribution and updating strategy.
In order to achieve that the following list of changes is proposed:
Migrate to the yarn package manager Migrate to the **7.11.*** or greater npm version
Create new org npm account to mange monorepository group
Split library packages into dependable sub-packages in bounds of current monorepository:
ala-n
commented
2 years ago
As an ESL architect, I want to have a more flexible distribution and updating strategy. In order to achieve that the following list of changes is proposed:
Migrate to the yarn package managerMigrate to the **7.11.*** or greater npm versionSplit library packages into dependable sub-packages in bounds of current monorepository:
@esl/core:esl-base-element
[tbd] esl-mixin-element
esl-traversing-query
esl-media-query
esl-utils
@esl/imageesl-image
@esl/mediaesl-media
@esl/alertesl-alert (??)
@esl/toggleablesesl-trigger
esl-toggleabe
@esl/panelesl-tabs (??)
esl-panel
esl-panel-group
@esl/popupesl-popup
esl-tooltip
@esl/footnotesesl-footnotes
@esl/scrollbaresl-scrollbar
@esl/selectesl-select
esl-select-list
@esl/carousel[tbd] esl-carousel
@esl/samples(name to be discussed)gh-pages
@esl/animateesl-animate
??
esl-a11ty-group (recommended for core but ...)
To Be Discussed:
[ ] migration strategy
[ ] build process
[ ] distribution process
[ ] versions and dependencies
[ ] migration script (?)
Priority High