Some days ago I had an interesting talk with a friend about how to organize code.
We were wondering how to share python code among several nodejs/TypeScript projects and avoid manual copy and paste or the implementation of an updater.
Since the day before I had prepared a boilerplate for a composer package for my colleague, a yarn package was the first stuff that I thought of!
That's it. The thing had intrigued me, seemed feasible and pretty simple.
Maybe I'll improve it in future.
At time of writing, the repo contains:
- dev/linux/build.sh -> a script to locally build the package in a docker container with node-alpine.
- package.json -> ready to build and publish new packages using yarn workspaces.
- python-src-code -> you won't believe it, but here you find the python code.
- yarn_packages -> I will surprise you: here the yarn packages. I've written a simple TypeScript function named
routineNameto wrap the execution ofmain.pyas POC.
Ofc, the names of the folders python-src-code, yarn_packages can (must, please) be renamed.