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

errorproject

v0.0.94

Published

401 Codefellows Midterm project using Javascript

Downloads

7

Readme

ohNoLogger

401 Codefellows Midterm project using Javascript

User Stories

Task List

UML Diagram

Getting Started on Prisma

Prisma Install Instructions


- npm install @prisma/cli --save-dev >>> to install prisma in cli
- npm install @prisma/client >>> install prisma client
- npx prisma init >>> creates schema.prisma file and .env file
- npx prisma introspect >>> to generate schema for each table in database
- npx prisma generate >>> update client side now we can send queries
- const { PrismaClient } = require('@prisma/client') >>> require this in your
- const prisma = new PrismaClient() >>> require this in your file

List of CLI commands:-

node query.js getRecord:

Shows you a list of errors stored in your database

+++++++++++++++++= PSQL Database +++++++++++++++++++++

In Terminal Create Database:

  • Enter: psql >>> Opens psql in terminal
  • \c into table >>> Lets you view a table
  • \dt describe table >>> lets you view whats in table.
  • Enter: CREATE DATABASE dbname; In .env:
`DATABASE_URL = postgres:localhost:5432/DATABASE-NAME`
To use schema file to start database:
`psql -f file.sql -d DATABASE-NAME`
Add to Heroku online, add this command to terminal:
`heroku pg:psql -f path/to/schema-file.sql --app your-heroku-app-name-here`

List of Common Commands:

- \l - to view all databases
- \c DATABASE-NAME - to navigate into your database
- \dt - to view the tables in your database
- \q to quit

Objectives

  • [ ] node.js documentation => access build in api methods

Explanation of Config Steps

https://notathoughtexperiment.me/blog/how-to-do-create-database-dbname-if-not-exists-in-postgres-in-golang/

https://docs.npmjs.com/misc/scripts

//get the users db URI and CLIENT ID

//do this with an inquirer function??

//use that db URI to set up a table called errtable

//maybe?? use fs to create .env in prisma folder

//TODO maybe?? symlink .env in prisma folder

//TODO write symlink from internal.env to prisma .env

//TODO after above script, run eblow commands in script in package json

//POST INSTALL COMMNADS //TODO then run prisma introspect //TODO then run prisma generate

```"postinstall": "rm ./prisma/.env && ln -s ./.env ./prisma/.env && npx prisma introspect && npx prisma generate",```

post install remove prisma .env file, sym link to .env in node modules, then run prisma intro and generate steps