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

@geut/xd

v1.6.1

Published

Run your lint and formatter in a single fast daemon.

Downloads

100

Readme

xd :laughing:

Build Status JavaScript Style Guide standard-readme compliant

Run your lint and formatter in a single fast daemon.

This project is based on eslint_d.

How it works

xd is a tool that detects your local lint and starts a daemon server so your next lint/format operations would run faster.

xd support eslint compatible engines.

We support the next engines:

  • standard
  • semistandard
  • standard + prettier
  • semistandard + prettier
  • eslint

Install

$ npm install -g @geut/xd

Usage

standard

Start by adding your lint dependencies locally:

$ npm install --save-dev standard

That's it, try to execute xd in your project:

$ xd *.js

To fix your file:

$ xd *.js --fix

standard + prettier

We include a prettier configuration for your standard lint that performs as a linter and formatter.

Prettier will run by:

  • Binary xd-prettier index.js
  • Option xd --prettier index.js
  • ENV variable PRETTIER=1 xd index.js
  • Detecting the presence of a .prettierrc config file in your project.

xd uses prettierx so you can use any of the next configuration files for your prettier:

  • .prettierrc
  • .editorconfig

eslint

xd will check your local binary eslint and configuration or it will use a fallback binary that we include.

No Server

Exists special cases where maybe you need to use xd without running a server.

You can use the binary: xd-ns or xd --no-server.

Help

$ xd --help

IDE Support

vim/nvim using ALE

let g:ale_javascript_eslint_use_global = 1
let g:ale_javascript_eslint_executable = 'xd'
let g:ale_linters = {
  \ 'javascript': ['eslint']
\}
let g:ale_fixers = {
  \ 'javascript': ['eslint']
\}

Issues

:bug: If you found an issue we encourage you to report it on github. Please specify your OS and the actions to reproduce it.

Contributing

:busts_in_silhouette: Ideas and contributions to the project are welcome. You must follow this guideline.

License

MIT © A GEUT project