Closed jboix closed 7 months ago
As a first iteration we will merge the demo using video.js awaiting the first release of pillarbox to integrate as an npm dependencyl
:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:
npm package (@main dist-tag)
Your semantic-release bot :package::rocket:
The goal of this issue is to separate the demo app from this repository for the following reasons:
rollup
for better flexibility.parcel
orvite
, which allows more straightforward configuration for fully-fledged SPA apps.While working on issue #175, we observed that the build process has become overly complex. The following issues have been identified:
We have tested the following alternatives:
Vite
It is easy to generate both ES and UMD modules with Vite. The demo page is handled correctly through multiple configuration files. However, dependency exclusion in the final build with Vite requires specifying each excluded dependency or building the library in SSR (Server Side Rendering) mode. See Building in library mode for node instead of browser This is a working example with SSR mode :
Rollup
Configuring Rollup for multiple targets in the SDK part is straightforward, offering extensive customization options. However, configuring the demo, especially serving it in a development server, becomes convoluted with multiple plugins and complex configurations. See this WIP configuration for the demo part:
Both solutions are not satisfying to contain the demo and SDK in the same repository, hence the decision to split them.