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

dsc-header-footer

v1.1.0

Published

This repository holds the sources to provide the DSC Header/Footer, as well as the Helmet for consumption on 3rd party sites.

Downloads

5

Readme

dsc-header-footer-helmet

This repository holds the sources to provide the DSC Header/Footer, as well as the Helmet for consumption on 3rd party sites.

Pipeline | Metrics

Build process

We use Rollup for providing a bundled version of Header/Footer and respective the Helmet. To provide these builds two scripts are defined in package.json.

yarn build:headerfooter
yarn build:helmet

Both commands can also be executed in an chained way using yarn build.

On build the relevant components for header/footer/helmet will be extracted out of the @salesforcedevs/dx-components package and then bundled as single JavaScript components.

The output for Header/Footer will be stored in /public/header-footer, and the output for the Helmet in /public/helmet.

For sites that use a REST based set up (Component Library and Metadata Coverage Report) relevant configuration files will be created under public/config.

QA

The helmet is consumed by apps like www.heroku.com, which has a staging app at www-staging.heroku.com (has basic auth: leave user empty, password is "ronin"). Those apps have a HELMET_HOST config var that can be pointed to your review app, making www-staging fetch the helmet from your PR:

heroku config-set HELMET_HOST=https://your-review-app-name.herokuapp.com -a www-staging

Remember to roll back www-staging after the QA process:

heroku rollback -a www-staging

Server setup

  • Assets are currently served from the https://developer.salesforce.com/shared-components URL (e.g: https://developer.salesforce.com/shared-components/helmet/import.js).
  • The developer.salesforce.com domain is served via Fastly, with the shared-components proxying to a Heroku app (e.g: Fastly fetches https://developer.salesforce.com/shared-components/helmet/import.js from https://dsc-header-server-p.herokuapp.com/helmet/import.js)
  • The Heroku app uses the static Heroku buildpack. The configuration is stored in the static.json file that sets HTTP headers for caching and CORS.

Example markup

The folder scripts/src/templates contains two example HTML files that showcase how to integrate the JavaScript files, and the custom elements.