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

@rlmartin-projen/projen-project

v0.0.34

Published

This is a projen template for creating other projen templates.

Downloads

1,345

Readme

projen-project

This is a projen template for creating other projen templates.

Usage

Creating a new projen template repo

npx projen new \
  --from @rlmartin-projen/projen-project \
  --projenrc-ts

Terminology: scaffolding vs generated

When creating a new projen project template, it is best to be clear about which files are generated once vs which are under control of the template.

Scaffolding

Scaffolding files are generated only once - at the time of project creation - and from that point forward are the responsibility of the developer. These can be edited freely and will never get overwritten by projen.

Generated

Generated files should never be touched by the developer, because the projen template will overwrite any changes. This is indicated even down to the the level of the filesystem, because generated files are marked as read-only. While developers can change those permissions, this is not advised because the subsequent run of npx projen will discard any manual edits made to those files.

Adding simple template files

Template files that are either static or use simple parameterization can be placed in either the files/scaffolding or files/generated folders.

Files with a .liquid extension will be run through the Liquid templating engine, with project-level options passed into the engine.

Files with any other extension will be copied as-is into the project.

Template file names are also run through the templating engine, and can thus include dynamic naming.

Convenience properties

For some commonly-used string properties, a convenience property is automatically injected and accessible for use in templates. These all begin with an underscore (_) and include sub-properties for common string formats: camel, kebab, pascal, snake, title. The currently-supported convenience properties are:

  • _name