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

@unfie/notes

v2.2.2

Published

Lab 04 for CF JS 401 Nights

Downloads

2

Readme

LAB: Advanced Mongo/Mongoose (04)

Notes Rev 04: CRD (update there, but not used) with collection abstraction (officially) and some polishes

Author: Earl Jay Caoile

Links and Resources

Documentation

Setup

To run locally, run npm i from the root directory. To install the package from npm, run npm i @unfie555/notes from the root directory. A package.json needs to exist for this to work. If it hasn't been created yet, create with npm init. Alternatively, you can create a package.json file with default by adding the -y flag: npm init -y

Configuring MongoDB

  • create an .env file on the top level of this repo defining the following variables:
MONGODB_URI=mongodb://localhost:27017/notes
PORT=3000

Note that this .env file will not come pre-configured as part of the npm published package, so the URL has been hardcoded into mongoose.connect as a backup option. If you want a different MONGODB_URI value, enter that into your .env file instead.

  • start your database with the path of the DB along with the folder location for your DB files (mongod --dbpath=/Users/path/to/data/db: i.e. "C:\Program Files\MongoDB\Server\4.2\bin\mongod.exe" --dbpath="D:\db" on Windows)

How to use package

Once the package is installed through npm or ran locally through the repo, users can enter the following commands:

  1. When a user adds a new note, it is saved to the database
  • notes -add “This is fun” –category school
  1. Users can list notes from the database
  • All Notes: notes --list or notes -l
  • Notes in a category: notes --list school or notes -l school
  1. Users can delete a single note
  • notes -d insertIDhere555

Tests

  • Testing command: npm test from the root directory.

UML

UML Image