For both weaver and tamu library components, the build process is very error prone.
It needs to be easier to build and develop a project without having to rely on publishing to npm.
It needs to be easier to build and develop a project without having to worry about weird/odd/unusual bugs resulting from the build process and configuration rather than from any code changes.
Consider the following improvement strategies:
Implement Verdaccio (https://verdaccio.org/) to automatically pull in local developemnt.
The build process is confusing with so many different subtle difference. Provide detailed documentation and step-by-step processes (on the internal wiki or github wiki as appropriate) while fixing any problems the documentation process reveals.
For both weaver and tamu library components, the build process is very error prone.
It needs to be easier to build and develop a project without having to rely on publishing to npm.
It needs to be easier to build and develop a project without having to worry about weird/odd/unusual bugs resulting from the build process and configuration rather than from any code changes.
Consider the following improvement strategies: