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

@zibuthe7j11/quia-sunt-neque

v1.0.0

Published

* Convert an absolute path to a tilde path: `/Users/YourUserName/dev` → `~/dev` * Inspired by [tilify](https://github.com/sindresorhus/tildify) by [Sindre Sorhus](https://github.com/sindresorhus) * Since tildify uses ES6 syntax, I created this package to

Downloads

2

Readme

@zibuthe7j11/quia-sunt-neque

  • Convert an absolute path to a tilde path: /Users/YourUserName/dev~/dev

  • Inspired by tilify by Sindre Sorhus

  • Since tildify uses ES6 syntax, I created this package to for those who use CommonJS environment.

Install

npm install @zibuthe7j11/quia-sunt-neque

Usage

const tildify = require('@zibuthe7j11/quia-sunt-neque');

tildify('/Users/YourUserName/dev');
//=> '~/dev'

Related

See un@zibuthe7j11/quia-sunt-neque for the inverse.

How to Contribute

Thank you for considering contributing to this project! Contributions are essential to keep the project thriving and improving. Below are steps on how you can contribute to the project:

1. Fork the Repository

  • Navigate to the repository on GitHub.
  • Click on the "Fork" button in the top-right corner of the page.
  • This will create a copy of the repository in your GitHub account.

2. Clone the Repository

  • On your GitHub account, find the forked repository.
  • Click on the "Code" button and copy the URL provided.
  • Open your terminal or command prompt.
  • Use the git clone command followed by the URL to clone the repository to your local machine.
git clone <repository_URL>

3. Make Changes

  • Navigate to the project directory on your local machine.
  • Make the necessary changes or additions to the files you want. Ensure your changes adhere to the project's contribution guidelines and formatting standards.

4. Commit Your Changes

  • After making the desired changes, save the files you have changed.
  • In your terminal or command prompt, navigate to the project directory.
  • Use the following commands to stage and commit your changes:
git add README.md # Replace README.md with the file you have changed
git commit -m "Brief description of changes"

5. Push Changes to Your Fork

  • Once committed, push your changes to your forked repository on GitHub:
git push origin main

6. Submit a Pull Request

  • Go to your forked repository on GitHub.
  • Click on the "Pull Request" button.
  • Provide a brief description of the changes you've made in the pull request.
  • Click on "Create Pull Request" to submit your changes for review.

7. Await Review and Feedback

  • Your pull request will be reviewed as soon as possible.
  • Be open to feedback and be willing to make further changes if necessary.
  • Once approved, your changes will be merged into the main project.

Thank You!

Thank you for taking the time to contribute to our project. Your efforts are greatly appreciated and help make the project better for everyone. If you have any questions or need further assistance, feel free to reach out via GitHub issues. Happy coding!