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

mo-convert

v1.0.0

Published

> ### Systematic [Motoko](https://github.com/dfinity/motoko#readme) base library type conversions.

Downloads

0

Readme

mo-convert  npm version GitHub license PRs Welcome

Systematic Motoko base library type conversions.


This repository includes Motoko source code and a JSON metadata file containing all base library type conversions with a consistent B.ofA : A -> B naming convention. mo-convert is intended as a stepping stone for community language tooling and for those such as myself who have trouble remembering whether the function was named Array.toBuffer() or Buffer.fromArray().

Quick Start (Motoko):

Add the following to your mops.toml config file:

[dependencies]
convert = "https://github.com/rvanasa/mo-convert"

Include the following import in your Motoko source code:

import C "mo:convert";

Go to town:

let nat = 123;
let text = C.Text.ofNat(nat); // => "123"

let option = C.Option.ofResult(#ok true); // => ?true

let array = [1, 2, 3];
let buffer = C.Buffer.ofArray<Nat>(array);

// Chain conversions with the piping operator
let pipe = (
  array
  |> C.Iter.ofArray _
  |> C.List.ofIter _
  |> C.Array.ofList _
);

Quick Start (Node.js):

Run the following command to install the mo-convert npm package:

npm i --save-dev mo-convert

Access the type conversion metadata:

const { conversions } = require('mo-convert');

console.log('All type conversions:', conversions);

Example JSON entry:

conversions[0] ==
{
  from: "Array",
  to: "Blob",
  module: "Blob",
  name: "fromArray",
  signature: "Blob.fromArray(bytes : [Nat8]) : Blob",
  prim: "arrayToBlob",
}