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

lancetyersemproj3

v1.0.0

Published

# Due: Wednesday, December 1st 11:59 PM CST

Downloads

4

Readme

Project 3

Due: Wednesday, December 1st 11:59 PM CST

Objective

The purpose of this project is to define automated workflows that can be utilized by Github Actions.

Problem Description

You will be making multiple workflows to accomplish tasks with Github Actions. When needing to send a notification email, use the email address [email protected].

Project Details

Before beginning the rest of this project, complete the following steps:

  • Make the main branch protected so that noone can directly push to it without going through a pull request and make sure that all status checks have to pass (add both as rules)
  • Write a simple NodeJS application (no webserver required) that contains a function for adding numbers together and returning the result
  • Read about Jest or Mocha tests and write a test for your NodeJS application

Once these steps are done, you will write workflows for the following:

  • Create a workflow that runs your tests on your NodeJS application using Github actions and both 12.x and 14.x versions of Node and produces a Github package if it succeeds. This should be done with two different jobs.
  • Create a workflow that runs will send an email when a pull request is created
  • Create a workflow that will add a label to your pull request when it is appropriately approved
  • Create two custom actions. The first is a Docker action that will write a file of random numbers. The second is a Javascript action that will read the file written by the first action, sum the values, and then print the resulting sum.

Some of these will require the use of community actions, while others require you to research uploading and downloading artifacts from actions. Once you have completed these workflows, you should have a basic understanding of how to create Github actions.

Submission Instructions

To submit the project, simply push your group's code to your repository. Each repository has a .gitignore in their directory to avoid pushing additional dependencies.