Home

Welcome to the didi wiki!

Just making some notes for the moment.

Given that cli client and config client are exactly that, clients, the consume other packages and so they include dev scripts.

The dev scripts uses tsc-watch --build {paths to all other packages needed} and the resulting success runs ts-node.

This compiles to release but does not update didi-js installed dependencies which come from npm registry. To get around this a Bootstrap script is included which symlinks the aforementioned dependencies with the release folder. But the final hurdle, the release srcs folder dependencies have not been installed so the bootstrap script should install the release folder dependencies ⚠️ or maybe further linking should point back to the source node modules because trying out new dependencies might be easier this way. It would be a good idea to .gitignore these node_modules / symlinks and the also the src folders and possibly delete them on release?

After all of this another ticket should be raised to clean up again and test, all our development workflow and release workflow should be ready to test from a clean install, dev a feature and then release. I should document as I go.