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

advanced-first-web-server-cw

v1.0.0

Published

A starter repo for the ACA Advanced `My First Web Server` project.

Downloads

2

Readme

My First Web Server

A starter repo for the ACA Advanced My First Web Server project.

Part 1.

  • Give your server the ability to respond to a GET request with a path "/users" and return the users array from state.js (use conditional)
  • Give your server the ability to respond to a GET request with a path "/users/1" and return the first user object from the users array from state.js (use conditional)
  • Give your server the ability to respond to a POST request with a path "/users" and just add a hard coded user object to the users array from state.js. .json() the last user in the array to send it back to the client. (if you do another GET request you should see this added)
  • Give your server the ability to respond to a PUT request with a path "/users/1" and just change any key value on the first user object in the users array in state.js. .json() this user to send it back to the client.
  • Give your server the ability to respond to a DELETE request with a path "/users/1" and remove one item from the users array. send() back a messsage "deleted"

Part 2. Use the express built in REST methods to do the same thing as Part 1

  • Give your server the ability to respond to a GET request with a path "/users" and return the users array from state.js
  • Give your server the ability to respond to a GET request with a path "/users/1" and return the first user object from the users array from state.js
  • Give your server the ability to respond to a POST request with a path "/users" and just add a hard coded user object to the users array from state.js. .json() the last user in the array to send it back to the client. (if you do another GET request you should see this added)
  • Give your server the ability to respond to a PUT request with a path "/users/1" and just change any key value on the first user object in the users array in state.js. .json() this user to send it back to the client.
  • Give your server the ability to respond to a DELETE request with a path "/users/1" and remove one item from the users array. send() back a messsage "deleted"

Part 3. Add the body-parser module to your project

  • Give your server the ability to handle a POST request with a path "/users" and add the data from the client to the users array
  • Assign an _id property to the user object that is a number that increments by 1 each time.
  • response.json() the user object to send it back to the client. (if you do another GET request you should see this added)

Part 4. Use path variables

  • Give your server the ability to respond to a GET request with a path /users/:userId and return the user object from the users array that has the _id == userId
  • Give your server the ability to respond to a PUT request with a path /users/:userId and just change any key value on the user object with this _id
  • Give your server the ability to respond to a DELETE request with a path /users/:userId and find the user with this id from the array. give this user object a new key value isActive:false. send() back a messsage "deleted"