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

@e3c-summer-worker/navigation-saturday

v1.2.2

Published

Making our custom headers is a bit involved. We have to copy a lot of HTML code into the scripts, and it's confusing and difficult to debug if something changes and goes wrong, especially if our only text editor is the one built into Squarespace.

Downloads

90

Readme

Navigation - Saturday Church

Making our custom headers is a bit involved. We have to copy a lot of HTML code into the scripts, and it's confusing and difficult to debug if something changes and goes wrong, especially if our only text editor is the one built into Squarespace.

Making the navigation in another component where you ethen import it is easier to debug and move around; you copy less code between pages and the development process is better if you're using something like VSCode.

We are using this folder to specifically host the desktop and mobile navigation component, that goes inside #headerNav and #sidecarNav in the Squarespace page, respectively.

The header code in public/index.html is almost exactly what you'd see copy and pasted into Squarespace (instead of importing the local .js file we use JSDelivr, and we need to add the contents in and styles.css.

Note that we are using yarn workspaces, so the installations will be mostly consolidated at a top-level node_modules/ folder.

Important

The site.css is the squarespace compiled css, and the styles.css are our styles.

Local Development

yarn
yarn start

Note that the styles will be quite a bit different than production, this is because I only copied a subset of the HTML into our public/ html file. The important thing is that the navigation bar is functional.

Also, when you switch to Desktop to Mobile view, refresh the page to get the functional navigation bars. Not sure why this is the case, maybe I didn't download all the files.

Production Build

yarn build

Usage

<script src="https://cdn.jsdelivr.net/npm/@e3c-summer-worker/navigation-saturday@1/build/navigation.js"></script>