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

@kano/web-components

v3.0.0-beta.2

Published

Shared web-components for the Kano ecosystem.

Downloads

14

Readme

Kano Web Components

A library of shared elements and behaviors for the Kano ecosystem

Docs & demo

Used in: Kano Code, Kano World (new codebase)

Development

After cloning the repo, install the dependencies in the main folder:

git clone [email protected]:KanoComputing/web-components.git
cd web-components
bower install

The components refer to their bower dependencies outside of their environment i.e. ../ and ../../. This is because web-components is meant to be a bower dependency itself. E.g. <link rel="import" href="../../iron-image/iron-image.html"> Therefore, a good practice is using Polyserve [link] that serves the component folders under ./bower_components/.

Polyserve's default port is 8080 and the components are accessible at http://localhost:8080/components/web-components/{componentName}.

For example, the kano-auth demo-page would be http://localhost:8080/components/web-components/kano-auth/demo/index.html.

To use the local version of web-components as a bower dependency, type bower link in the web-components folder and then bower link web-components in the project folder where you want to use it. Be aware though that Gulp can't handle symlinks (in which case manual copy-pasting of the dependency folder offers a solution).

Releasing on Github

When a new release is due, you can update the release in the Kano Web Components repository [link].

Migration to Polymer 2.x

Listed here are all the components defined in this repository. Initally developed using Polymer 1.x, we now intent to move progressively towards Polymer 2.x.

To work on the migration, use the bower-2.x.json file and rename it to bower.json (backing up the original bower.json). Clean and reinstall your bower dependencies. This will update all the third party libraries to their 2.x version. The imports for a 1.x element will now point to the Polymer compatibility layer for 2.x

This list indicates the status of the migration:

hyb = hybrid

[hyb] kano-api-client-behavior [hyb] kano-drop-down [hyb] kano-modal [hyb] kano-progress-api-behavior [hyb] kano-share [hyb] kano-step [hyb] kano-user-summary [hyb] kano-auth [hyb] kano-drop-down-item [hyb] kano-nav [hyb] kano-progress-bar [hyb] kano-share-card [hyb] kano-style [hyb] kano-cart [hyb] kano-gamification [hyb] kano-nav-bar-icons [hyb] kano-project-card [hyb] kano-share-feed [hyb] kano-tracking [hyb] kano-circle-progress [hyb] kano-glint-animation [hyb] kano-notifications [hyb] kano-reward-modal [hyb] kano-share-stats [hyb] kano-user-badge [hyb] kano-circle-spinner [hyb] kano-icons [hyb] kano-particle-burst [hyb] kano-secondary-links [hyb] kano-share-wrapper [hyb] kano-user-menu [hyb] kano-alert (Breaking change: As of shadow DOM v1, the slotted selector can only style top level elements. To style the buttons inside a kano-alert component, place them at the top level) [hyb] kano-comment-report [hyb] kano-lightboard-preview [hyb] kano-primary-links [hyb] kano-session [hyb] kano-sound-player-behavior [hyb] kano-user-stats

Usual issues experienced with the kano components:

  • style tag being outside of the template (A warning will be generated)
  • @apply(--whatever) => @apply --whatever
  • in demos: wrap style is="custom-style" in a custom-style element (web-components v1 spec)