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

wildcards-components

v0.1.0

Published

Components created by the Wildcard Team

Downloads

4

Readme

Wildcards Component Library

Components created by the Wildcard Team

Dev Setup

Quick start

Make sure you have Node version >= 6.0 and NPM >= 3

Clone the repo, install and then start adding/editing components inside /src/lib

# clone the gaf-ng-app-starter repo and rename it (renamed 'new_awesome_lib' below)
git clone [email protected]:meltwater/wildcards-components.git wildcards-components

# change directory to our repo
cd wildcards-components

# install the repo with npm
npm install

# start the sandbox app
npm start

Navigate to https://local-social.sysomos.com/settings/account

Development

NPM link

NPM link allows you to develop locally without publishing the npm package. If you are just working on your component, there is not need to use npm link, the sandbox app will work fine. But if you need to test your component in the consuming project, while making changes, npm link is right for you.

In wildcards component library

cd dist/wildcards-component
npm link

In consuming library

npm link @meltwater/wildcards-components

To continuously run the build on change(recommended when using npm link) you will want to run the build:watch script in the wildcards component library. Furthermore, you may want to enable a watcher on the consuming library to build when node_modules/@meltwater/ changes.

NPM scripts

  • npm start: Runs npm run sandbox:serve
  • npm run build: Generate bundles and typings
  • npm run build:watch: Run build in watch mode (build will re-generate on save of any file in the src/dist directory)
  • npm run sandbox: Generate library bundle using npm run build and start sandbox web app using webpack dev server
  • npm run docs: Generate API docs for the library using [compodoc] ()
  • npm run docs:watch: Run docs generation in watch mode (docs will re-generate on save any file in the src/lib directory)
  • npm run test: Run unit test suite
  • npm run lint: Lints code using tslint

Generated from

https://github.com/meltwater/gaf-ng-lib-starter