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

fraternal

v0.1.2

Published

🐑 A framework for creating clone-able project templates that still compile

Downloads

17

Readme

Fraternal

A framework for creating clonable project templates that still compile

Intro

This is a proof of concept right now and will be unstable until it's first release. There will be breaking changes as it grows, but I think there is some potential here.

Example template

Motivation

I've used Cookiecutter in projects before, but it always bummed me out that when I wanted to populate variables in code the syntax would cause the template to no longer compile. This made it hard to maintain these templates as time went on. You would need to make the changes you wanted to and then clone the template to test it.

So this project has some goals as it is being built

1. Templates must compile

This is a huge factor for maintaining templates. You should be able to have a test suite and start the template if you want.

2. Template syntax must be customizable

This project is being made with Typescript templates in mind (that's like 99% of what I use) but it should be able to be used for any language.

3. Configuration should be painless

Besides just having a simple configuration, it should also be helpful to the developer. Someone wanting to setup a template shouldn't have to keep going back to documentation to figure out how to do something.

Currently this is achieved with a javascript file being the template, but this requires that the template has a package.json to get the typescript types. This is probably the thing that will evolve the most before version 1.