npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@sjcrh/proteinpaint-rust

v2.84.0

Published

Rust-based utilities for proteinpaint

Downloads

322

Readme

Rust-compiled utilities

This directory holds the source code for rust-compiled utilities.

Code layout

All source code files should be directly under the src/ directory. For a source code file to be compiled, create a [[bin]] entry for it in the Cargo.toml file:

[[bin]]
name="tool0"
path="src/tool0.rs"

[[bin]]
name="othertool1"
path="src/othertool1.rs"

Note that the default package.autobins has been disabled, so that we avoid using the src/bin subdirectory to hold uncompiled source code files. The convention in the Proteinpaint project is to put bundled or compiled code under a bin/ folder, which goes against rust cargo's assumptions of having source code under src/bin.

Using from nodejs

// assuming a js file from server/src 
const run_rust = require('@sjcrh/proteinpaint-rust').run_rust
// or 
// import * as utils from './utils'

// 'indel' may be replaced by any binary name as specified in Cargo.toml
const out = await run_rust('indel', input_data)

Test

From the proteinpaint/server directory,

npx test

Build

npm run build # cargo build --release

The compiled dependencies and target binaries will be generated under ./target/release.

Release

Use Github Actions to coordinate the release of related package updates. The package versioning, build, and deployment uses the standard npm tooling under the hood (version, pack, and publish, respectively).