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

way2web-filter

v0.2.5

Published

Making filters fun again.

Downloads

11

Readme

Way 2 Filter

NPM version Downloads

Add the js-filter-body class to the element with all items to filter.

The class js-filter-counter will receive the amount of items, based on the filters.

The class js-filter-item must be added to all items.

The class js-filter-option must be added to every filter link.

The class js-filter-sort must be added to every sort link.

Filter links

The filters links has also data attributes.

So the link with the class js-filter-option has also a attribute data-filter-key, this contain the key of the filter.

The data attribute data-filter-option contains a value.

You can add a i element, this will receive the class fa-check if you click on the filter link.

Filter items

The items has also data attributes.

If the filter link has the value 'city' as value in the attribute data-filter-key.

Than you have a data attribute data-filter-city at the item.

The value of the data attribute must be a value of a data-filter-option.

Example of a filter link:

<li class="js-filter-option" data-filter-key="city" data-filter-option="Utrecht">
    <a href="#">
        <i class="fa fa-check fa-fw text-muted"></i>
        Utrecht
    </a>
</li>

Example of a sort link:

<a href="#" class="js-filter-sort" data-filter-sort="city" data-filter-order="asc">
    <i class="fa fa-check fa-fw text-muted"></i>
    City
</a>

Example of a item:

<ul class="element | list-unstyled | js-filter-body">
    <li>
        <a
            class="js-filter-item"
            data-filter-city="Utrecht"
        >
            ...
        </a>
    </li>
    ...
</ul>

Test the package.

To test the package, clone the package to your system. Than run this command.

npm run build

This will copy the test files to the dist, and also build the package files include the dependencies.

When this script is complete without errors, you can open dist/index.html in your browser. Open the dev tools, tab console, and you see all the results of the tests.

If you only want to check the eslint rules, just run.

npm run lint