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

neoman-engine

v1.0.0-alpha044

Published

Neoman templating engine.

Downloads

10

Readme

npm version Build Status Windows Build status dependencies Status devDependencies Status codecov

MIT License PRs Welcome Code of Conduct

Neoman engine

neoman - Old Saxon. None, nobody.

A template manager that intends to be nobody and nothing; it doesn't want to impose. Neoman knows that your code shouldn't have to become a project template, because it already is one. :relieved:

Basic Usage

Drop the following folder and file into your project, and Neoman will have all it needs.

MyProject/.neoman.config/template.json

or

.neoman.config/template.json MyProject/ (you can also put it in parallel and adjust the root attribute).

A minimal template.json would look like this:

{
    "name": "My Project Template",
    "description": "My useful project template will lead many to triumph.",
    "author": "Noh Body",
    "url": "https://en.wikipedia.org/wiki/Outis",
    "identity": "myprojtmp",

    "input": {
        "use": "prompt",
        "define": {
            "namespace": "What will the root namespace of your project be?"
        }
    },

    "transform": [
        { "subject": "my.project.namespace", "with": "{{namespace}}" }
    ],

    "#": "You don't need 'files' if you want the 'transform' and 'pathTransform' sections to apply to all files",
    "files": ["**/*.ts"]
}

Once your project is ready, setup a folder to store your templates, and copy the project folder there. Then, it's ready to use via neoman.io.

Documentation

For documentation, please refer to the wiki.