This project has two high-level goals:
Methodology TBD. A first pass might be to try and consume the CSS output in the form of theme modules that work for particular component libraries. For example, vaadin components are highly extensible and can consume themes. Material components can consume custom properties, etc
There are some noteworthy community initiatives to make bootstrap-flavored webcomponents with which there may be potential synergies
project | comments |
---|---|
web-padawan/aybolit | solid work, still ramping up on component coverage |
morbidick/bootstrap-webcomponents | not yet evaluated |
nik-christou/lit-element-bootstrap | looks very promising |
smart elements | doesn't work under shadow dom |
Additionally, the bootstrap maintainers seem agreeable to webcomponents.
twbs/bootstrap
has eliminated jQuery and also now contains ESM for each component. It could be possible to make web components that just consume those existing bootstrap esm classes. Initial research into this approach indicates it would require a lot of orchestration among the host component and the bootstrap classes.. may be better, lighter, easier and more efficient to just implement components
To get a feel for different options, this repo has started implementing a component
See packges/button
npm install
-- install dependenciesnpm run build
-- generate/compile all the thingsnpm run start
-- serve the demos