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

bharyang

v0.0.3

Published

Core library for bharyang extensions.

Downloads

10

Readme

Bharyang npm Build Status npm

Core library for bharyang extensions.

This is the core library that provides functions to rearrange the block of lines.

It was mainly written due the OCD nature of mine and my colleagues.

// Before:                                      |  // After:
                                                |
import get from 'lodash/get';                   |  import React from 'react';
import { browserHistory } from 'react-router';  |  import moment from 'moment';
import moment from 'moment';                    |  import get from 'lodash/get';
import React from 'react';                      |  import camelize from 'camelize';
import { connect } from 'react-redux';          |  import { connect } from 'react-redux';
import { bindActionCreators } from 'redux';     |  import { bindActionCreators } from 'redux';
import camelize from 'camelize';                |  import { browserHistory } from 'react-router';

Whenever we see imports like this, we can't help but give it a little cringe. It's not wrong in any way, but its just... not pretty. How about arranging them in a way so that you would want to give a second look at your code?

Waste of time? Totally. We actually spend ridiculous amount of time just to make the code "look pretty". But hey, once it's done, that satisfaction is totally worth it.

Actually, we are just so used to this ladder styled code that we can't go back 😅.

Anyways, "Bharyang" (Nepali) translates to -> "Ladder".

Yup, so creative! Thank you. 👏

Implementations

Currently it is implemented for Visual Studio Code only. Check here for the actual use.

Usage

import {sortImports} from 'bharyang';

sortImports(selection);

API

  • sortImports(text: string)
  • sortAscending(text: string)
  • sortDescending(text: string)