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

vedas

v1.0.10

Published

A hackable, extendable, functionally-composable way to go about dealing with wrangling types in JavaScript. Auto-casting, coercion, and type inference for the Alice in WOnderland world that is JS runtime.

Downloads

10

Readme

Vedas

Auto type casting, coercian, and inference like the weakest, loosest wizard on the JavaScript block.

NPM: Vedas Lib

Contributors Forks Stargazers Issues MIT License LinkedIn

IMPORTANT!!

WIP, but dev is very active and rolling along fast. Expect a working version release within the next day or two.

About Vedas

Product Name Screen Shot

Built With

Getting Started

This is an example of how you may give instructions on setting up your project locally. To get a local copy up and running follow these simple example steps.

Prerequisites

Installation

  1. Install Vedas

Using npm

  npm install vedas

Using yarn

  yarn add vedas

2(a). import or require Vedas anywhere in your codebase (default, top-level module export continue reading below for additonal exports)

Using import

  import vedas from 'vedas'

Using require

  const vedas = require('vedas')

2(b). import or require Vedas anywhere in your codebase as destructured, namespaced exports.

Using import

  import { exportOne, exportTwo  } from 'vedas'

Using require

  const { exportOne, exportTwo } = require('vedas')

Usage

Use this space to show useful examples of how a project can be used. Additional screenshots, code examples and demos work well in this space. You may also link to more resources.

For more examples, please refer to the Documentation

Roadmap

See the open issues for a list of proposed features (and known issues).

Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE for more information.

Contact Meh'

Branden Dane - @God_Dane - [email protected]

Project Github Repo
https://github.com/DaneTheory/Vedas

Acknowledgements

Big shout-out to Sindresorhus for creating well-documented, solid codebase's that made finding code snippets needed to get this out quickly a breeze to stalk down and steal ;)

A strong thank-you indeed to the wonderful folks at Mozilla and all the sexy-goodness they put into crafting excellent documentation.

The tooling driving the magic behind this lib's build pipeline

And ofcourse, non of this would have been possible without the Goose and Iceman to my Maverick, beer and coffee.