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

project-chef-templates

v1.0.8

Published

Templates for project-chef CLI

Downloads

3

Readme

Welcome to project-chef-templates 👋

license npm

Templates for project-chef CLI

Template Structure

📦framework-name
 ┣ 📂extras
 ┃ ┗ 📂extra-package-name
 ┃ ┃ ┣ 📂init
 ┃ ┃ ┃ ┣ 📜injector.config.json
 ┃ ┃ ┃ ┗ 📜other config files
 ┃ ┃ ┗ 📂main
 ┃ ┃ ┃ ┗ 📜main files to be copied
 ┣ 📂init
 ┃ ┗ 📜index.js
 ┗ 📂main
 ┃ ┗ 📜main files to be copied

There are 3 entry points for a framework template, main, init, extras Either main or init is required or both, extras is optional if you want extra packages to be added.

main

The files here are copied directly to the target

init

An index.js is required for this directory, the default export of this index.js file is ran while creating your boilerplate in the cli. The init files index.js needs to be in es5 format.

I used this to ran commands like create-react-app, gatsby-cli and nextjs. You can adjust it to your own needs.

extras

Here appears the packages that are optional for the user who selected your framework in the cli to create the boilerplate. Every main directory is a standalone package to be installed.

There are 2 entry points for an extra package, either one is required or both.

main

The main files of the extra package to be copied to main directory.

init

This directory is for injecting extra config to the main framework directory For example, you want to add plugins to babel.config.json, install npm packages

For these purposes an injector.config.json is required To install npm packages add package names to the lists:

  • packages

  • devPackages

To alter the main config files the field configs is required this field takes json objects as input,

{
  file:"babel.config.json"
  appenders:["plugins"]
}

The field file is the reference config for the Injector API to get the fields that you want to add to target config, config files must be in json format, copy the config file next to injector.config.json

The fields you want to have as reference and target to alter should be appended to field appenders

For example I want to add plugins to babel.config.json,

Add plugins to appenders, this will read the reference babel.config.json's plugins field, and add the plugins to the target babel.config.json

If you want to alter a nested field use . like: field.nested.target

injector.config.json template

Note: leave the fields empty if not used, all the fields must be present in injector.config.json

Note: to a field, whose value type is a list, the values needed are appended. to a field, whose value type is not a list, the value provided by injector.config.json is replaced with the current value.

Examine the existing templates for further understanding

Please contact me if there is a problem or a question :)

Author

👤 Tolga Erdönmez

Show your support

Give a ⭐️ if this project helped you!


This README was generated with ❤️ by readme-md-generator