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 🙏

© 2025 – Pkg Stats / Ryan Hefner

slim-code-generator

v1.1.0

Published

A script for creating files with boilerplate code based on a template

Downloads

18

Readme

Slim-Code-Generator

Small script to automate generating boilerplate code.

How?

This is a cli tool. To use, just run generator in your terminal and follow the prompts.

All files created are created in the directory where the generator cli is called.

For the prompts:

Template: Provide "jest", "presentation", "container". Or you can provide the shorthand: 'j' for jest, 'p' for presentational, 'c' for container. Anything else is invalid and no code will be generated.

File: The name of the file as you want it to appear in your directory without any prefix.

Examples:

Jest

Template: jest File: foo

output: foo.spec.js was added

// import React from 'react';
// import { shallow } from 'enzyme';
// import { Foo } from './foo.js';

describe('Foo', () => {
  let component;

  beforeEach(() => {
    // component = shallow(<Foo />);
  });

  xit('renders', () => {
    expect(component).toBeTruthy();
  });
});

Note: You'll need to have Jest and Enzyme configured in your application for this test to run. Also, you should recognize that this test will be marked pending until you modify the generated code. This is good because sometimes you need to create unit tests on code that already exists. This test wont break until you're ready to check it.

Presentation

Template: presentation file: foo

output: foo.js was added

import React from 'react';

const Foo = (props) => (

);

export default Foo;

Container

Template: container file: foo

output: foo.js was added

import React, { Component } from 'react';

class Foo {
	render() {
		return (

		);
	}
}

export default Foo;

Roadmap

  • More templates: Create github issues with templates that you want to use. This tool can be used to create any file based on any template. Additional arguments could be added in promps based on the template prompt.