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 🙏

© 2025 – Pkg Stats / Ryan Hefner

lbcamden-frontend

v1.0.7

Published

LBCamden Frontend contains the code you need to start building a user interface for London Borough of Camden products.

Downloads

352

Readme

LBCamden Frontend The src directory

Structure

GOV.UK Frontend is broken into a number of layers in order to help provide a logical structure, loosely following the conventions of ITCSS.

  1. Settings
  2. Tools
  3. Helpers
  4. Core
  5. Objects
  6. Components
  7. Utilities
  8. Overrides

Each folder has its own entry point (_all.scss).

Settings

Global variables for the project, for example colour palettes and spacing and typography scales.

This layer should not output any CSS.

Tools

Mixins or functions that implement either logic (e.g. conditionally outputting CSS) or calculations, and that need to be made available globally.

This layer should not output any CSS.

Helpers

Mixins that abstract common styling (for example, focus states or visually hidden content)

This layer should not output any CSS.

Core

Basic content styles for typography, links etc. The classes defined in this layer would generally correspond to an HTML element - for example paragraphs, headings, lists or links.

Objects

Objects can range from something as simple as a wrapper element, to layout systems.

They may be used in any number of unrelated contexts to the one you can currently see it in. This means that making modifications to these types of class could potentially have knock-on effects in other places.

Components

Discrete pieces of UI. In most cases these will map to the components in the Design System.

Utilities

Utility classes – for example clearing floats, visually hiding content.

Overrides

Classes that map to a specific property – for example margin or font weight - and override all other layers. Rules in this layer will generally be marked as !important.

Class names within this layer use an additional prefix -!-, for example .govuk-!-font-width-regular.

If a class only overrides when a condition is met, the condition will be at the end of the class name. For example .govuk-!-display-none-print will only override with display: none in a print layout.