feat: initial wasm/ts/js bindings

[baszalmstra]

This PR adds initial bindings for a WASM port of some functionality of rattler. This PR aims to add a framework, more bindings can be added later.

At this point only Version and VersionSpec are exposed in a fashion that I think meets the standards of this library.

Uses wasm-pack to create a WASM binary of Rust code including a javascript wrapper. This is then double wrapped in a typescript library that provides a more ergonomic API. Tests have also been added.

Im not an expert in this area, feedback is welcome!

Fixes #1078.

If CI succeeds Ill do an initial upload of this package to npmjs.org. But we still need to find a good home for it on npmjs.org since rattler is already taken.

[trim21]

is @conda/rattler taken on npmjs？

[baszalmstra]

Thats indeed the name Im going for but Im not a member of the @conda organization. I put some feelers out to figure out who owns it and if I can contribute to it.

[baszalmstra]

I uploaded the current state to https://www.npmjs.com/package/@baszalmstra/rattler @trim21 does this help you?

[trim21]

looks good.

Some ideas:

the JsVersion and JsVersionSpec may be a little bit confusing because it's not version of js but a conda package version

[baszalmstra]

Those should never be used, they are internal types. You should only need Version and VersionSpec.

[trim21]

I think we also need Version.components to get details of version and Version::cmp to compare versions.

There is no api to know if a version is a pre-release(only is-dev but not alpha/beta/rc) and there is no api to compare which version is newer

[trim21]

ParseStrictness is missing from npm distribution

[baszalmstra]

I can add all of that when I find the time.

But feel free to create PRs against this PR, or can we merge this already @wolfv ?

[trim21]

The current npm distribution is broken. the ./pkg/ directory is referenced by dist but it's not uploaded

[trim21]

I can add all of that when I find the time.

But feel free to create PRs against this PR, or can we merge this already @wolfv ?

Version.components is private and can't be used in wasm crate, can we export it?

Or should we add is_pre_release/is_stable method to Version crate?

[wolfv]

Happy to merge and iterate in PRs. I know that some other folks from @QuantStack are also potentially interested (in the solver functionality, particularly).

[baszalmstra]

Version.components is private and can't be used in wasm crate, can we export it?

What do you need this for? There are a number of higher. level methods to modify the version that can be used instead.

Or should we add is_pre_release/is_stable method to Version crate?

Conda does not define what a pre release is. There is "isDev" though

[trim21]

Conda does not define what a pre release is. There is "isDev" though

Thanks, I didn't know that 😄

This is because when you upgrade your version with tools, normally you don't want to upgrade from "stable" (pep440 for example) to "unstable" version.

If conda doesn't have "pre release" I have no more problems.