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

twiglint

v0.0.14

Published

Linter for the twig templates

Downloads

34

Readme

TwigLint [WIP][ALPHA]

Twig templates linter

Install


    npm install twiglint -g

Usage

    Usage
      $ twiglint <filename>

    Options
      -s, --silent Show only errors
      -f, --format Use a specific output format - default: stylish [compact]
      -d, --debug Write debug file, and prepend every check with filename
      -h, --help  This help

Rules to be included

For now rules are hardwired, there will be configurable config, and external plugins in the future

  • [x] Warn if there is no only in include function (no-only)
  • [x] Variables declared, but not used (no-unused-vars)
  • [x] Variables used without declaration, or docblock (no-undeclared)
  • [x] Do not use closing bracket on selfclosing tags (\/> => >) (no-closed-self-closing-tags)
  • [x] Prefer camelcase variable naming (prefer-camel-case-vars)
  • [x] Do not use spaceless tag (no-spaceless)
  • [x] Wrong tab padding on logic brackets (tags-padding)
  • [ ] use staticUrl functions for resources
  • [ ] Spelling

Roadmap

  • [x] Write tests for plugins
  • [x] Maximum usage of the parser
  • [x] Visual reporter with the ability to jump to the needed line (compact)
  • [x] Plugins as seperate modules
  • [x] cli testing
  • [ ] Write pluggable logic for external plugin
  • [ ] Allow to use local config
  • [ ] Sublime/VSCode/PhpStorm extentions

Docblock formatting

{# @param {string} imageLink #}
{# @param {string} view_change_uri  #}
{# @param {int} user_location_id #}

or

{# 
    @param {string} imageLink
    @param {string} view_change_uri 
    @param {int} user_location_id 
#}

License

MIT