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

@northeastern-web/global-elements

v1.1.1

Published

Northeastern global elements built with Tailwind CSS and Alpine.js.

Downloads

7,089

Readme

Global Elements Package

Dependencies

  • NodeJS >= 12.x
  • NPM >= 8.x
  • kernl(ui) >= 2.x

Development

Builds

To build the project locally and prepare it for production use, run the following in the project's root directory:

  1. npm install
  2. npm run build

Preview (MacOS/Linux/WSL)

Note: To preview the Global Elements in your local development environment, ensure you have PHP configured on your machine:

  1. php -S localhost:8080

Github Workflow

Feature Branching

  1. Create a new Issue in the Global Elements Github repository. Provide as much context as needed for the issue
  2. Checkout develop branch then create a new feature branch off of develop with the issue number and title (e.g. git checkout develop && git checkout -b issue-1/remove-trailing-slash)
  3. Make fix in feature branch and create new commit with changes. Push changes to remote Github repository (e.g. git push origin issue-1/remove-trailing-slash)
  4. See Github merging and releasing workflow below

Merging and Releasing

  1. Create new Pull Request (PR) in the Github Repository to merge the feature branch into the develop branch
  2. Add a developer from Web Solutions team to review and approve the merge.
  3. Once merged, test the build on https://dev-global-packages.cdn.northeastern.edu/

Releases

This repository follows the major.minor.patch semantic versioning scheme.

To create a new release tag, run the following in the project's root directory: git tag -a v1.x.x -m "Release version x.x.x" where x.x.x is equal to the major.minor.patch semantic version.

Patches

For minor fixes or patches (no new features, fixes to existing features only), increment the ending patch version (e.g. v1.0.17 becomes v1.0.18).

Features

If there are large backwards-compatible (non-breaking) changes such as refactors or new features are being introduced, a new minor version release tag should be created (e.g. v1.1.0).

Large updates that are not backwards-compatible will require a major release (e.g. v1.0.18 becomes v2.0.0)

Usage

For up-to-date usage information, visit the kernl(ui) Global Elements documentation