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 🙏

© 2026 – Pkg Stats / Ryan Hefner

angular-autowrap

v0.6.2

Published

An easier and less noisy way of doing validation and designing control template in angularjs

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

zpbappizpbappi

Keywords

angularwrapautowrapvalidationtemplate

Readme

Angular AutoWrap

Build Status Coverage Status Code Climate

Why?

Here's the complete history, if you are interested.

Getting it

I use git tags to build a version automatically inside travis. Each tag is released in npm, bower and GitHub Releases simultaneously. Here's how you get it:

npm

npm install angular-autowrap

bower

bower install angular-autowrap

GitHub Releases

You will find all the releases here.

Building from source

Make sure that you have gulp installed globally. Then, on the project root folder, run the following commands in sequence:

npm install
gulp build

Output of the is ideal for development, as it is sourcemapped with individual components. For production use, I would recommend using the version found in npm, bower or GitHub Releases. However, if you want to use the latest source code, then run

gulp release

and use the build in your project.

Running the tests

Quite easy actually. Just run

npm install
gulp test

Using it

Yet TODO...

For now, check the example folder.

FAQ

1. How come you deploy customized packages in npm, bower and GitHub from travis? Ans: Isn't that cool? I know! Here is a post describing how I did it.

2. Why don't you write any documentation and usage example demonstrating the features? Ans: The reason is quite simple. I don't like to write documentation nearly as much as I like to code. But, trying to develop the habit now. You will see some progress soon.

3. Then why don't you have any test? Ans: That is a sin. I am working on that right now. There will be no additional feature development before I have it under test coverage. FYI, "not having test" is the main reason behind the version being 0.x.x yet. I do now. And, it feels great to have tests.