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

@quoine/translate

v0.0.1

Published

Quoine Translate for Landing Page

Downloads

38

Readme

[DEPRECATED]

In favour of modern-package-boilerplate

Build Status Coverage Status dependencies Status devDependencies Status

Features

Getting started

  1. Clone this repo from github
  2. Inside repo directory run npm install && rm -r .git && git init
  3. Update package.json with your information

Usage

Commands

npm run clean

Delete all cache and output files

npm run dev

Build your library in development mode

npm run build

Build your library in production mode

npm run test

Run tests

npm run test:watch

Run tests in watch mode

npm run cover

Cover your code (Work with ES6)

npm run coveralls

Sends coverage details to coveralls.io. Used in .travis.yml and should not be used manually.

npm run lint

Check your code for errors and code styles

npm run prepublish

Hook for npm, that executes when you publishing package in npm repository.

Lint

This boilerplate uses air-bnb code style conventions, however if you don't like it, you can disable it, by removing the following line in .eslintrc config file:

{
  //...
  
  "extends": "airbnb"
}

Webpack aliases

If you are as tired as me to write '../../../' in the require statements, you can use alias feature provided by webpack. Here is an example of aliases, built in this boilerplate by default (builder/resolve.js):

resolve: {
    alias: {
        Src: path.resolve(process.cwd() + '/src'),
        Lib: path.resolve(process.cwd() + '/lib')
    }
}

Feel free to add your custom aliases, they are awesome.