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

@riteable/project-meta

v1.0.5

Published

Extract project metadata from various files.

Downloads

24

Readme

project-meta

Extract project metadata from various files, such as package.json, .env, and Sass files.

Why

To generate a web app manifest file you need data such as the following:

{
    "name": "My App",
    "description": "A short description of the project.",
    "background_color": "#ffffff",
    "theme_color": "#000000"
}

Generally, you would already have this data set in different files. The name might be set in a .env file; the description in package.json; and the colors in a Sass variables file. This module extracts the data from all these files, and makes them available to use wherever you need it.

Install

Install the package:

$ npm i @riteable/project-meta

Example usage

The following shows a use case involving webpack and the webpack-pwa-manifest plugin:

// webpack.config.js
const projectMeta = require('@riteable/project-meta')
const WebpackPwaManifest = require('webpack-pwa-manifest')

const meta = projectMeta({ sass: './src/css/_variables.scss' })

module.exports = {
  // ...
  plugins: [
    new WebpackPwaManifest({
      filename: 'web-manifest.json',
      name: meta.env.appName,
      short_name: meta.env.appName,
      description: meta.package.description,
      background_color: meta.sass.bodyColor.hex
    })
  ]
  // ...
}

Options

projectMeta(options = {}) accepts the following options:

  • package: Path to the package.json file. Default: process.cwd() + '/package.json'.
  • env: Path to the .env file. Default: process.cwd() + '/.env'.
  • sass: Path to the Sass variables file. Default: false.
  • camelize: Set to false to keep text case as is. Default: true.

Output

The following output is an example:

{
    package: {
        name: 'my-app',
        description: 'A short description of this app.'
    },
    env: {
        appName: 'My App'
    },
    sass: {
        bodyColor: { r: 0, g: 0, b: 0, a: 1, hex: '#000000' }
    }
}

NOTICE: The module transforms the variables to camel-case by default. So, environment variables like APP_NAME will be turned into appName, and Sass variables such as $body-color will become bodyColor.