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

pomy

v1.6.3

Published

Based on the concept of a project object model (POM), POMY can manage a project's build, reporting and documentation from a central piece of information.

Downloads

267

Readme

POMY



Welcome to POMY

Pomy is a software project management and comprehension tool. Based on the concept of a project object model (POM), Pomy can manage a project's build, reporting and documentation from a central piece of information.

Install

$ mkdir project-name && cd project-name
$ npm install pomy -g

Pomy depends on Node.js and npm.

Configuration

Your project need to be configured using JSON in a pomy.json file.

{
  "group": "lico.atom",
  "artifact": "pomy-test",
  "version": "1.0.1",
  "name": "pomy-test",
  "title": "pomy-test - test pomy tool",
  "description": "test pomy tool",
  "private": false,
  "license": "MIT",
  "debug": true,
  "skin": "default",
  "define": "cmd",
  "keywords": "JSRT, Node.js, Gulp, Angularjs, Markdown, API Document, JsDoc, Open Source",
  "repository": {
    "type": "git",
    "url": "[email protected]/licoliu/pomy-test.git"
  },
  "bugs": {
    "url": "http://github.com/liujc/pomy-test/issues"
  },
  "homepage": "http://github.com/liujc/pomy-test",
  "dependencies": {},
  "devDependencies": {
    "pomy": "^1.0.1"
  },
  "site": {
    "domain": "127.0.0.1",
    "port": 8421,
    "user": "root",
    "nohup": true
  },
  "manual": {
    "url": "http://github.com/liujc/pomy-test",
    "email": "[email protected]"
  },
  "registry": "https://registry.npm.taobao.org",
  "googleWebmasterMeta": "",
  "author": "lico",
  "developers": [{
    "id": "lico",
    "name": "lico liu",
    "email": "[email protected]",
    "url": "https://github.com/licoliu"
  }],
  "contributors": [],
  "organization": {
    "name": "atomunion",
    "url": "https://github.com/atomunion"
  },
  "target": "local"
}

Usage

If you want to pack your project:

$ pomy package --target release --version 1.0.1

The syntax for running Pomy is as follows:

$ pomy [<phase>] [options]
  • All available options are listed below:

    --target release/snapshort/local/test/...

    --version x.xx.xxx

  • The built in life cycles and their phases are in order are:

    clean - pre-clean -> clean -> post-clean

    default - validate -> dependancy -> initialize -> generate-sources -> process-sources -> generate-resources -> process-resources -> compile -> process-classes -> generate-test-sources -> process-test-sources -> generate-test-resources -> process-test-resources -> test-compile -> process-test-classes -> test -> prepare-package -> package -> pre-integration-test -> integration-test -> post-integration-test -> verify -> install -> deploy

    site - pre-site -> site -> post-site -> site-deploy

A fresh build of a project generating all packaged outputs and the documentation site could be done with:

$ pomy clean && pomy package && pomy site

Just creating the site and running it can be done with:

$ pomy clean && pomy site && pomy site:run

Just Formating all js, css, sass, scss, less and html files can be done with:

$ pomy format

or

$ pomy format-js && pomy format-css && pomy format-html

Just Fetching all js dependancies can be done with:

$ pomy dependancy

Just executing all unit test cases can be done with:

$ pomy test

This is the most common build invocation for a Pomy project.

When not working with a project, and in some other use cases, you might want to invoke a specific task implemented by a part of Pomy - this is called a goal of a plugin. E.g.:

$ pomy archetype:generate

There are many different plugins avaiable and they all implement different goals.

Support

Contributing

We welcome contributions of all kinds from anyone.

License

Copyright (c) 2009~2016 lico and other contributors(https://github.com/licoliu/pomy/graphs/contributors)

Licensed under the MIT License