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

cluedin-integration

v2.0.46

Published

cluedin-integration

Downloads

4

Readme

cluedin-integration

COMPONENT DESCRIPTION GOES HERE

Demo & Examples

Live demo: dervalp.github.io/cluedin-integration

To build the examples locally, run:

npm install
npm start

Then open localhost:8000 in a browser.

Installation

The easiest way to use cluedin-integration is to install it from NPM and include it in your own React build process (using Browserify, Webpack, etc).

You can also use the standalone build by including dist/cluedin-integration.js in your page. If you use this, make sure you have already included React, and it is available as a global variable.

npm install cluedin-integration --save

Testing

npm test - run tests

npm run test:watch - watch tests

npm run test:coverage - generate test coverage report

Tests use Enzyme and snapshots. If the strucutre of a component changes the test may fail with a warning. To update the snapshot run npm run test:watch and press u for any outdated snapshot that can be updated.

Static type-checking

The project uses Flow Type to statically type check the code base. Type definitions are stored in flow-typed/cluedin/*.js. The project also uses the flow-typed project to provide type definitions for dependencies. Babel is used to strip out the type usage during the build process.

npm run typecheck - type check the code using flow

References:

Flow Flow-typed

Usage

EXPLAIN USAGE HERE

var CluedinIntegration = require('cluedin-integration');

<CluedinIntegration>Example</CluedinIntegration>

Properties

  • DOCUMENT PROPERTIES HERE

Notes

ADDITIONAL USAGE NOTES

Development (src, lib and the build process)

NOTE: The source code for the component is in src. A transpiled CommonJS version (generated with Babel) is available in lib for use with node.js, browserify and webpack. A UMD bundle is also built to dist, which can be included without the need for any build system.

To build, watch and serve the examples (which will also watch the component source), run npm start. If you just want to watch changes to src and rebuild lib, run npm run watch (this is useful if you are working with npm link).

License

PUT LICENSE HERE

Copyright (c) 2016 CluedIn.