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

@carvalhopa/random-words

v1.0.3

Published

random words

Downloads

1

Readme

Random Line

This library returns a random line for a given file, but you must provide your own file.

Preparing your environment

Pushing your code there

  • Create a new repository, and push this code there.
  • run npm login
  • run npm init
  • Make sure to include your username on the package name. Example: @melomario/random-line

A wild new file appears, and it's called package.json.

Writing your first test and function

Ok. It's time to learn how to manage our dependencies. You can run the following command to add a test framework to your project:

npm install --save-dev jest or a shortcut: npm i -D jest

The --save-dev or -D section establishes that the jest framework is not going to be necessary in production. We'll use it to validate our code, but we don't need it bloating our production servers, right?

If you look into the package.json file, you'll see a new command. This command is used to run tests: npm run test. Try it on your terminal.

💡 Exercise 1 💡

  • There's a test with small problem. Find it and fix it.
  • Also, try to add more words to the sample file assets/words.txt and run your tests again

💡 Exercise 2 💡

Now it's time to publish (the first version) of your library! Make sure you insert some new words on your words file and then run npm publish --access public