typeshare VS crates.io

It doesn’t generate a complete client but 1Password’s Typeshare can generate TypeScript from Rust data structures https://github.com/1password/typeshare

Aren't there things like typeshare to aid with that case?

Sure. I would love some help. I am visiting my family all March (I am typing this from the airport), so I don't know how much time I'll have to work on trane for the next month. But maybe that gives you some time to use it, and read the code and docs.

I am not going to put my personal email here, and I don't see an option to send private messages on hn, although it's probably out there somewhere. Probably in the commits, lol. Worst case, feel free to open an issue on the trane repo.

As a first ask, what do you think of this: https://github.com/1Password/typeshare?

I figured writing the UI in rust is probably not a good idea. The ecosystem for UI is very immature and the language itself is probably overkill. But doing it in typescript/html/css requires you to understand the internal data structures (all the JSON files you see in the courses are just serialized rust objects).

I found that repo and it seems like a promising approach to autogenerate the types and make the interaction easier.

How does this compare to typeshare?

Recently, 1Password open-sourced Typeshare, to help Rust developers create FFI (foreign function interfaces). Curious to learn more? Join the team behind the tool this week on Zoom at 11a Eastern to discuss Typeshare and answer any questions.

Newly open-sourced project that might be handy for some of you all https://github.com/1Password/typeshare

Typeshare by 1Password, the original inspiration for this blog post. It's available on crates.io.

For sure! We actually open sourced an early version of it a while back (https://github.com/1Password/typeshare), but it became a slowdown to work on it both for our own internal needs and for the outside world, so that was abandoned and it's since fallen out of sync with the project internally today.

Rust has a rich ecosystem of frameworks and libraries that let you read, parse, and manipulate text files, interact with cloud services and databases, and perform any other job that your project's development workflow may require. And because of its strong typing and tight memory management, you are much less likely to write programs that behave unexpectedly in production.

All the code discussed in this article can be accessed through this repository. For integration with existing projects consider using keyword_extraction crate available on crates.io.

So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. There’s a good chance the crates you need are available in Rust's crates.io repository.

The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.

Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.

Before proceeding, let's check https://crates.io/, the official Rust package registry.

The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.

5. Crates.io

When using crates from eg. crates.io, and also things like std and core

Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.