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

toolopedia

v1.0.5

Published

Simplifying big codes for small tasks in a single word

Downloads

9

Readme

toolopedia

npm version

Table of Contents

A message from Prasun Bairagi

Hi folks, thanks for using this library as your helping tool.
For your ease, I have provided the methods along with description, a proper usage and output in the Tools Available section.
Any suggestions !?, please help me to grow it by contributing to my Github repo and make it more useful.

Installation

Step 1

npm install toolopedia

Step 2

import yourfavname from 'toolopedia';

Step 3

Use methods by adding . and method name to your imported name yourfavname.methodname();

Tools Available

| Methods | Description | Usage | Output | | --- | --- | --- | --- | | sortAStr() | Sort your string and get a string. | sortAStr( 'Hello' ) | eHllo | | removeDupWordsFromAStr() | Remove duplicate words from a string. | removeDupWordsFromAStr( 'Hello can I use use tools' ) | Hello can I use tools | | removeDupLettersFromAStr() | Remove duplicate letters from a string. | removeDupLettersFromAStr( 'Hello' ) | Helo | | convertNewDateIntoDDMMYYYYOnlyWithSlash() | fetch date only from new Date() or 'yyyy-mm-ddThh:mm:ss.sssZ' and convert into DD/MM/YYYY | convertNewDateIntoDDMMYYYYOnlyWithSlash( '2024-03-29T12:52:58.693Z' ) convertNewDateIntoDDMMYYYYOnlyWithSlash( new Date() ) | 29/03/2024 29/03/2024 | | convertNewDateIntoMMDDYYYYOnlyWithSlash() | fetch date only from new Date() or 'yyyy-mm-ddThh:mm:ss.sssZ' and convert into MM/DD/YYYY | convertNewDateIntoMMDDYYYYOnlyWithSlash( '2024-03-29T12:52:58.693Z' ) convertNewDateIntoMMDDYYYYOnlyWithSlash( new Date() ) | 03/29/2024 03/29/2024 | | convertNewDateIntoYYYYMMDDOnlyWithSlash() | fetch date only from new Date() or 'yyyy-mm-ddThh:mm:ss.sssZ' and convert into YYYY/MM/DD | convertNewDateIntoYYYYMMDDOnlyWithSlash( '2024-03-29T12:52:58.693Z' ) convertNewDateIntoYYYYMMDDOnlyWithSlash( new Date() ) | 2024/03/29 2024/03/29 |

Contribution

Thank you for considering contributing to Toolopedia! Contributions are what make open-source projects such a powerful tool for the community. Whether you're reporting a bug, proposing a feature, or contributing code, your help is greatly appreciated.

How to Contribute

  1. Fork the repository.
  2. Clone the forked repository to your local machine.
  3. Create a new branch for your feature or bug fix: git checkout -b feature/your-feature or git checkout -b bugfix/your-bug-fix.
  4. Make your changes and test them thoroughly.
  5. Commit your changes: git commit -m 'Add some feature' or git commit -m 'Fix some bug'.
  6. Push to the branch: git push origin feature/your-feature or git push origin bugfix/your-bug-fix.
  7. Open a pull request against the master branch of the original repository.

Code Contribution Guidelines

  • Ensure your code follows the existing code style and conventions.
  • Write clear and concise commit messages.
  • Provide a detailed description in your pull request explaining the changes made.

Bug Reports and Feature Requests

If you encounter any bugs or have ideas for new features, please open an issue on GitHub. We welcome all feedback!

Get in Touch

If you have any questions or need further assistance, feel free to reach out by opening an issue or contacting the project maintainer directly.

Let's collaborate and make Toolopedia even better together!