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 🙏

© 2026 – Pkg Stats / Ryan Hefner

cloud-ramp-sdk

v1.1.2

Published

SDK for creating WebAssembly code for Cloud Ramp

Downloads

345

Readme

Official Cloud RAMP SDK

This package exists to help users write their code for cloud-ramp applications. A user must write their code using this package before uploading it to our website to assure it can be properly deployed.

Your code will be compiled using AssemblyScript, which is a subset of TypeScript that can be safely compiled to a WebAssembly module. This can be done using the command npm run asbuild, and your module will be located in the outFile location, as listed in the asconfig.json file.

Usage

  1. Download the module

A user must first initialize a new project and run npm i cloud-ramp-sdk. If no package.json file exists in your project, we will initialize a blank one for you. In addition, we will add a number of scripts that are to be run when building your code. Those are: asbuild, asbuild:release, and asbuild:debug.

  1. Write the code

Once you have installed our package, you should see a directory structure as follows:

assembly/
| env.ts 
| index.ts
| sdk.ts
| tsconfig.json
| user.ts
node_modules/
asconfig.json
package-lock.json
package.json

You should only need to worry about modifying the code within user.ts, as it contains the necessary functions to run a Cloud-RAMP applications. If you do not care about running code on one or more of these events, simply leave it blank.

In order to write you code, you will need to access the set of exported functions that we give you in sdk.ts. An example function can be seen below:

export function onJoin(event: WSEvent): void {
  log("User " + event.connectionId + " called onJoin");

  const ctx = new Context();
  const setRes = ctx.db.set("userId", event.connectionId);
  if (setRes.isError()) {
    log("Error setting userId: " + setRes.error);
    return;
  }

  const getRes = ctx.db.get("userId");
  if (getRes.isError()) {
    log("Error getting userId: " + getRes.error);
    return;
  }

  log("User ID fetched from database: " + getRes.data);
}
  1. Compile your module

Once you have written your code, you will need to compile it to a WebAssembly module so that we can properly run it. To do this, run the command npm run asbuild. Once this is complete, you can find your module where the release.outFile property of the asconfig.json file points. By default, it will be in build/release.wasm.

  1. Upload your code

If you have not already made an account on our website, that will be the first step. Once this is complete, navigate to the dashboard, hit the "Create new service" button, and upload your code. You can also modify existing services by selecting the name of a previous upload, and uploading a new module.