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

@enalmada/clone-code

v0.1.1

Published

make source into template

Downloads

27

Readme

clone-code

A means of turning repeatable patterns in your source code into template through comments.

All existing solutions (that I could find with reasonable search time) require you to copy your code into separate files. It just isn't practical to keep these templates in sync with rapidly evolving codebase. Every refactor is double the work. Editors don't handle these file types well.

Supports

  • copying file to another file
  • copy block of code
  • add new union type ex: "const entities = 'two' | 'one';" -> "const entities = 'three' | 'two' | 'one';"
  • add TODO comments (for things that just can't be templated but shouldn't be forgotten)

For example, this source:

/* ENTITY_HOOK
{
  "toFile": "test/outputs/<%= h.changeCase.lower(name) %>.ts",
  "replacements": [
    { "find": "Source", "replace": "<%= h.inflection.camelize(name) %>" }
  ]
}
*/

export class Source {}

Turns into

export class NewEntity {}

Getting Started

Read the documentation website

See nextjs-boilerplate for full usage example.

TODO

  • [ ] validating comment hook data
  • [ ] not changing data within hooks

inspiration

Contribute

Using changesets so please remember to run "changeset" with any PR that might be interesting to people on an older template. Although this isn't being deployed as a module, I would like to call out things worth keeping in sync.