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

@poratta/website

v0.1.0

Published

Pharos acts as a guiding light to helps us create consistent, dependable and focused experiences for all of JSTOR users.

Downloads

1

Readme

MDX

Documentation pages on the Pharos site are written using MDX — markdown files that allow you to integrate JSX easily. This combines the ease in editing long-form content with being able to import components which can elevate the content. These file names should be kebab-cased and named to match the component and what will be displayed in the side navigation bar.

Pharos components

Components used in the documentation can be found in /src/components. Examples of them being used and imported can be seen in other existing MDX files found in pharos-site/src/static. Please use the <PageSection> component for each documentation category and use its subSectionLevel property for subsections under the category. For best practices, also use the <BestPractices> component

Adding page to side-navigation bar

When creating a new section or page of documentation, it is important to add a link to the page in the sidenav so that users can readily navigate to the page. This involves accessing the sidenav component in pharos-site/src/components/Sidenav.tsx and adding the newly made page to the appropriate array, which will generate a link in the sidenav automatically. Consequently, it is important to follow the naming conventions mentioned in the MDX section.

Making a pull request

Once a page has been created or documentation has been modified, you can then generate a pull request indicating the changes made.