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

@weareenvoy/ajinomoto-theme

v0.0.4

Published

Ajinomoto starter theme

Downloads

2

Readme

🚀 Quick Start

mkdir my-site
cd my-site
yarn init
# install @weareenvoy/ajinomoto-theme and it's dependencies
yarn add gatsby react react-dom @weareenvoy/ajinomoto-theme
# install linting packages
yarn add gatsby-plugin-eslint @danbruegge/gatsby-plugin-stylelint stylelint
  • Then create a new gatsby-config.js file in the root:
module.exports = {
  plugins: [
    {
      resolve: '@weareenvoy/ajinomoto-theme',
      options: {
        brand: 'lingling' // or 'taipei'
      }
    }
  ]
};
  • Add configured .eslintrc.js and .stylelintrc.js files to the root of the project. These can be found in the envoy-gatsby-base repo.

  • Add contentful .env.* files. These can be found in Envoy's shared LastPass space.

You can now run your gatsby site using:

yarn gatsby develop

🛠 Overriding theme

Styles

To override theme's SCSS:

yarn add gatsby-plugin-sass node-sass

Create gatsby-browser.js file in root and add import your main.scss file. You can now make changes to individual scss files.

Pages and components

  • To override any page, name your file with the same name as the page you're overriding in src/pages. Caveat to this is you'll lose contentful queries from the npm package so you need to recreate them.

  • To override props, import from @weareenvoy/ajinomoto-theme:

import { HomePage, Box } from '@weareenvoy/ajinomoto-theme'

Doing more with themes

  • Further reading on building Gatsby themes here.

  • Use of yarn/npm is up to you.

Gatsby suggests using yarn workspaces like the gatsby-theme-examples repo does, but using yarn link or npm link is a viable alternative if you're not familiar with workspaces.