Currently the libraries are built using Webpack and generate a "build" folder containing "umd" files.
this was acceptable in terms of POC but the final state should be as follows:
1) use Rollup instead of Webpack
2) produce a "lib" folder as output
3) produce ESM and CJS versions of the same build in the folder according to rollup config provided.
4) make sure dependencies are not bundled in for production execution
5) dependencies can be bundled in development mode (please reason on why and how)
6) typescript declaration files to be also available in the lib folder
7) demonstrate consumption of the built package
Currently the libraries are built using Webpack and generate a "build" folder containing "umd" files.
this was acceptable in terms of POC but the final state should be as follows: 1) use Rollup instead of Webpack 2) produce a "lib" folder as output 3) produce ESM and CJS versions of the same build in the folder according to rollup config provided. 4) make sure dependencies are not bundled in for production execution 5) dependencies can be bundled in development mode (please reason on why and how) 6) typescript declaration files to be also available in the lib folder 7) demonstrate consumption of the built package
ESTIMATION: analysis: 1d development: testing: