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

secretkeeper

v1.3.1

Published

```sh npm i secretkeeper ``` ## Usage ``` js const express=require("express"); const app=express(); const secretkeeper=require("secretkeeper"); const secrets=new secretkeeper.Manager({username:"guest"}); const port=process.env.PORT || 3000; app.use(secret

Downloads

1

Readme

This package is a middleware for managing secrets to not show the client

This is mainly meant to be used with express.js

Installation

npm i secretkeeper

Usage

const express=require("express");
const app=express();
const secretkeeper=require("secretkeeper");
const secrets=new secretkeeper.Manager({username:"guest"});
const port=process.env.PORT || 3000;
app.use(secrets.middleware);
app.get('/', (req, res)=>{
    const {usernam}=req.query;
    secrets.addSecret("username", usernam);
    res.send("logged in");
});
app.get('/dashboard', (req, res)=>{
    console.log(req.secrets);
 if(req.secrets.username && req.secrets.username!="guest"){
     res.send("Logged in")
 }
 else{
     res.status(405).redirect("/");
 }
})
app.listen(port, console.log(`listening on ${port}`));

Explanation

the secretkeeper package gives you a Manager class. we create an instance of the manager class using. Creating this needs an object, the default value for secrets

const secrets=new secretkeeper.manager({username:"guest"});

secretkeeper middleware needs to be used to store secrets inside of the session.

app.use(secrets.middleware);

To add a secret we call:

secrets.addSecret(id, value);
//Remember, secrets is the instance of Manager class we created

Whenever you specify secrets.middleware in app.use, all the secrets get stored in req.secrets where req is the request variable in the callback when specifying a route There are 2 ways to get a secret. If you have specified the middleware, req.secrets[secret_id] will give you access to the secret with id of the secret_id variable. Or you can also call secrets.getSecret(secret_id) to get the same result The third method is the deleteSecret(id) method- This deletes a secret with the given id