we would add prefixes to the version tags going foward (rust-x.y.z etc).
Now that we have all of this we could roll with it, but by now I got the feeling that we should have just done it in separate repos, where the NPM repo just includes the Rust package as a dependency. Then all the above workarounds become unnecessary.
The workarounds above incurs a mental overhead to anyone looking at this repo - separate repos would be straight forward to understand and work with.
Potential downside: development of new features could be a bit more difficult as one would have to use a dev-version of the Rust package in the NPM repo to develop a feature in both repos at once.
This repo contains both the Rust package and the NPM package. To accomplish this, we are swimming against the tide quite heavily:
rust-x.y.z
etc).Now that we have all of this we could roll with it, but by now I got the feeling that we should have just done it in separate repos, where the NPM repo just includes the Rust package as a dependency. Then all the above workarounds become unnecessary.
The workarounds above incurs a mental overhead to anyone looking at this repo - separate repos would be straight forward to understand and work with.
Potential downside: development of new features could be a bit more difficult as one would have to use a dev-version of the Rust package in the NPM repo to develop a feature in both repos at once.