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

compy

v0.1.31

Published

component js boilerplate js project

Downloads

115

Readme

NPM version Dependency Status Build Status compy - lightweight app builder/compiller

Compy is a lightweight approach for developing web apps (framework/lib agnostic). Based on TJ's component package manager it allows you to install components and use them in your code right away. Compy makes your development fun because:

  • you can install and use components without any configurations
  • you can use local require
  • you can use coffeescript, sass, jade and other plugins
  • you can run karma tests
  • you will have livereload with simple static server

watch screencast for live intro.

##install

$ npm install compy -g

##plugins compy can use component's plugins to extend it's functionality. For example if you want to use coffee in your project, you need to npm install component-coffee in your project's folder.

compy was tested with following plugins:

cli comands

  Usage: compy <command> [options]

  Options:

    -h, --help                 output usage information
    -V, --version              output the version number
    -d, --dir <path>           project source path. Must contain package.json
    -o, --output <path>        output directory for build/compile
    -v, --verbose              verbosity
    -f, --force                force installation of packages
    -s, --staticServer <path>  custom server that serves static with compy middleware
        --dev                  install dev dependencies

  Commands:

    install [name ...]      install dependencies or component
    compile                 compile app (in dist folder by default)
    build                   build the app (compile and minify sources)
    server [watch]          run static server. If "watch" option enabled - watch changes, recompile and push livereload
    test                    run karma tests
    watch                   watch and rebuild assets on change
    plate [appname]         generate boilerplate package.json
    graph                   show all dependencies/versions installed

config

The configuration for compy sits in package.json inside compy namespace. main is an entry point of your app and the only required property.

{
  "name": "appName",
  "version": "0.0.0",
  "description": "my awesome app",
  "main": "index.js",
  "license": "BSD",
  "compy": {
    "dependencies": {
      "component/jquery": "*"
    },
    "main": "app.js"
  }
}

writing tests

To run karma based tests with compy. The package.json configuration should be adjusted and all required karma plugins should be installed. For example to run mocha tests with sinon and chai inside phantomjs following configurations should be set:

{
  ...
  "compy":{
     ...
     "tests":{
      "frameworks":[
        "mocha", "sinon-chai"
      ],
      "plugins":[
        "karma-mocha",
        "karma-sinon-chai",
        "karma-phantomjs-launcher"
      ]
    }
  }
}

And plugins should be installed locally.

$ npm install karma-mocha karma-sinon-chai karma-phantomjs-launcher

now with compy test all *.spec.js files will be runned as a mocha tests.

license

MIT