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 🙏

© 2025 – Pkg Stats / Ryan Hefner

attyc

v0.1.10

Published

Command line app to verify types in an angularjs template

Readme

ATTyC

Currently in Alpha

AngularTemplateTypeChecker is a command line tool that uses typescript to verify angularjs templates. You supply the names and types of the variables that the template uses, and attyc will find any bugs in your template.

Note: Attyc isn't intended to conclusively prove that a template is correct, AFAIK this is impossible in angularjs. Its goal is to give you a bit more confidence that the template is correct. If you want absolute confidence that your templates don't contain errors, upgrade to angular 2 and use the AOT compiler.

Getting Started

To install run npm install -g attyc. For help, run attyc --help.

Attyc needs some metadata about your template to work out the types of template variables. It expects there to be a comment at the very top of the template, containing an edn vector of maps containing the keys :name (variable name), :type (variable type) and optionally :import (path to import the type from). For example:

<!-- [{:name "ctrl" :type "Controller" :import "./controller"}] -->

Once you've added this metadata, run attyc [glob matching template files]

Known Issues

  • Attyc works best when you use the "controller as" syntax. If you don't, you'll have to specify every single scope variable you use in the template metadata (ain't nobody got time for that).
  • Other than in the ng-init, ng-repeat and ng-options attributes, variable declaration is not allowed. For example, {{ x = 10 }} will cause an error.
  • Attyc assumes that if an attribute contains a variable name, then it is an angular expression. This may not always be true.
  • Filters are not type checked (although arguments to filters are). This could potentially lead to attyc missing errors. This may change in future.

Building it yourself

  • Clone the repo
  • Run npm install
  • Make sure you have leiningen installed
  • Run lein figwheel
  • In another terminal, run node dist/main.js
  • Figwheel will rebuild the code whenever it changes

For a production build, run lein cljsbuild once prod.