In Debian, we'd like to take corresponding source of each module and build then in debian. This means we can't take the npm dist tarballs because they only have the generated files. Tags of this repo has the full repo, so even if we download tags corresponding to a module version, we still have to exclude all other modules from the tarball. I see two possible solutions.
Include the typescript source with the modules published in npmjs.com (this would be the simplest option I think).
If the above option can't be considered, can you provide module-source via npmjs.com or via github releases ? May be that can be automated via github actions https://github.com/softprops/action-gh-release Would you be open to a merge request to setup this action ?
Release everything with a single tag/version like lodash does, each module can be just a file.
I would consider option 2 if you want to make a PR, I'm not really interested in maintaining 1. Three is also possible but seems like unnecessary churn.
In Debian, we'd like to take corresponding source of each module and build then in debian. This means we can't take the npm dist tarballs because they only have the generated files. Tags of this repo has the full repo, so even if we download tags corresponding to a module version, we still have to exclude all other modules from the tarball. I see two possible solutions.
Reference https://stackoverflow.com/questions/7106012/download-a-single-folder-or-directory-from-a-github-repo