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

@grapheng/units

v0.0.5

Published

GraphQL types for common units of measurements

Downloads

3

Readme

Units

An experimental collection of GraphQL Types to represent units of measurement in various systems.

Getting Started

Install

npm i -D @grapheng/units

Use

Output types: Minimal Example:

import { Distance, Rounding } from "@grapheng/units";

const schema = makeExecutableSchema({
  typeDefs: gql`
    ${Distance.GraphQL.outputType.typeDefs}
    ${Rounding.typeDefs}

    type Query {
      myQuery: DistanceOutput!
    }
  `,
  resolvers: {
    DistanceOutput: Distance.GraphQL.outputType.resolvers,
    Query: {
      myQuery: () => ({ meters: 3 })
    }
  }
});

For Input types, writing

import { Distance } from "@grapheng/units";

gql`
  ${Distance.GraphQL.inputType.typeDefs}
`;

into your schema is enough to start using DistanceInput anywhere. However, the library also exports a convenience function with each module to help use the type in your code.

Below is an example that offers a flexible API for input (for example { feet: 4, inches: 2 }) but uses this function to convert it ultimately to millimeters (4 feet 2 inches => 1270 millimeters)

import { Distance } from "@grapheng/units";

const resolvers = {
  Mutations: {
    addPieceOfLumberToInventory: (source, args, context) =>
      context.DB.addPieceOfLumberToInventory(
        args.boardType,
        Distance.convertInput(args.boardLength).millimeters
      )
  }
};

Experiment

cd into this package and npm run start then open http://localhost:4000/graphql in your browser

Further Development TODOs

Bugs

  • fix moment library drift (1000 years -> milliseconds -> years)

General Improvements

  • make types better

Implement new types

  • location -> tries to go out and get stuff async
  • price / or specific types like dollar?

Complete API Re-Design:

  • export each package individually?
  • investigate making graphql queries completely flexible (e.g. fuel efficiency -> miles per gallon, or km per milliliter, etc.)