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

interactive-map-front-end-plugin

v1.1.1

Published

Interactive map front end plugin.

Downloads

3

Readme

Interactive Map Front End Plugin

Rollup based javascript library featuring Babel 7, ESLint, flow, jest, ESDoc, Rollup, semantic-release and live debugging.

Getting Started:

This boilerplate including a basic code to start creating a js based library.

Start with cloning the project:

$ git clone --depth=1 git://github.com/Ziv-Barber/library-boilerplate.git your-project-name
  • Remove the .git directory (rm -rf your-project-name/.git).
  • Edit package.json and change the name of the project to your project name.
  • The boilerplate without any changes supporting creating a library for both CommonJS, es6 modules, amd and browser. If you don't need all of this then just edit the rollup.config.js file and remove the inputs that you don't need.

Now, create a new github project and do:

$ git init
$ git remote add origin https://github.com/your-name/your-project-name.git
$ git add -A
$ npm run commit
$ git push origin master

This project is using semantic-release to automatic handling of the version of your library. To be able to automatic release a new version you must configure Travis-CI to your new project:

  • Go to https://travis-ci.org/ and either signup or signin.
  • Select your new project and click setting.
  • You MUST configure a token or semantic-release will not be able to commit changes:
    • Create a new token (see here how to do it).
    • Permissions needed in the github token:
      • repo:
        • repo:status
        • repo_deployment
        • public_repo
      • admin:org:
        • read:org
      • admin:repo_hook:
        • write:repo_hook
      • user:
        • user:email
    • In your Travis-CI project setting, go to the environment settings section and add a new environment variable with the name 'GH_TOKEN' and the generated token as the data.
  • To test everything just push something into github and it should update everything automatic!

Allow doing npm publish automatically by semantic-release:

  • You need a npm token (see here) and add it as the NPM_TOKEN environment variable to Travis-CI like you did with the GH_TOKEN for github.
  • Update the release section in package.json and add '@semantic-release/npm' to both 'prepare', 'publish' and 'verifyConditions'.

External dependencies:

This project is using the following awesome libraries/utilities/services:

Installation:

via yarn:

$ yarn add library-boilerplate

via npm:

$ npm install library-boilerplate

The API:

To create the library api:

$ yarn esdoc

or:

$ npm run esdoc

:coffee: The source code:

The project structure:

- library-boilerplate/lib/ - All the sources should be here.
- library-boilerplate/lib/types/ - All the flow type declarations.
- library-boilerplate/__tests__/ - All the unit tests.
- rollup.config.js - The configuration for [rollup](https://rollupjs.org/).
- .editorconfig - The [coding style settings](https://editorconfig.org/) for this project.

Npm scripts:

When using with yarn then use the following syntax:

$ yarn name params

Or with just npm:

$ npm name params
  • start - Run the code in development mode.
  • build - Build the production mode.
  • lint - Lint :cop: using ESLint.
  • flow - Flow checks.

Variations:

  • library-boilerplate (this project) - Rollup based javascript library boilerplate featuring Babel 7, ESLint, flow, jest, ESDoc, Rollup, semantic-release and live debugging.
  • library-boilerplate-mocha - Rollup based javascript library boilerplate featuring Babel 7, ESLint, flow, mocha, ESDoc, Rollup, semantic-release and live debugging.
  • react-boilerplate - React 16.5 based frontend boilerplate featuring Babel 7, ESLint, flow, Jest, ESDoc, Webpack 4, React 16.5, Redux, redux-thunk, semantic-release and react-hot-loader debugging.
  • react-boilerplate-mocha - React 16.5 based frontend boilerplate featuring Babel 7, ESLint, flow, mocha, ESDoc, Webpack 4, React 16.5, Redux, redux-thunk, semantic-release and react-hot-loader debugging.

Credit:

  • Created by Ziv Barber.