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

@springernature/global-details

v2.0.0

Published

A JS-independent, accessible disclosure component

Downloads

4,700

Readme

Global Details

The global-details component is for collapsing sections of content and making them expandable. SOme call this a "disclosure pattern". It uses <details> and <summary> and, as such, is JavaScript independent. In older browsers, the sections are expanded by default.

Usage

First, import the global-details styles—selecting the brand settings you require.

@import '../node_modules/@springernature/global-details/scss/10-settings/default';
@import '../node_modules/@springernature/global-details/scss/50-components/details';

Then compile the template located in the ./view folder whenever the component is needed. See the ./demo/context.json to see an example of the expected data.

Variants

open

You can make a details instance open/expanded by default (on page load) by applying open: true to the data used to compile its template. This adds the open attribute to its <details> element.

headingLevel

By including a headingLevel property with a number (of type String) you can add heading semantics to the summary’s title. This is recommended in most cases, since these components typically represent collapsed sections of the page.

With headingLevel: '2', the markup for the header becomes:

<div class="c-details__header" role="heading" aria-level="2">
    ...
</div>

listItem

If you set listItem: true, the outer class="c-details" element becomes an <li>. Where heading semantics are not provided (see headingLevel), list semantics are recommended. In general, use heading semantics where a set of successive details instances represent large sections of content. Use list semantics where each instance discloses only a sentence or two.

Be careful to wrap the set of <li> instances in a <ul>.