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

coda-auth

v1.2.4

Published

Static Authentication for Next.js

Downloads

5

Readme

Next.js + Authentication

WARNING

This does not use dynamic values. This is currently for personal use and has values hardcoded for my setup. You probably should be using npm next-auth instead. Please do use this in anykind of production environment. That being said you can follow through my edits if you want to fork a version for yourself.

Purpose

Fork of npm next-auth which used a runtime environment variable of NEXTAUTH_URL to determine base url of authentication. When using the serverless-next.js Severless Framework Component it will be deployed at Lambda@Edge. This does not allow the use of adding environment variables and thus conflicts with the way next-auth handles routing. This package instead searches the lambda name for occurances of -prod- or -dev- and will pick a static base url from that. Where does it get the static base url? It is hardcoded right now. So, you probably should avoid this package unless you too want to fork and hardcode.

List of Edits

  1. created /dist/config.js
  2. specified a personally used url to become the export when lambda@edge -prod- or -dev- is found in the lambda name
  3. import this config into /dist/client/index.js a. any mentions of process.env.NEXTAUTH_URL will now also search for a url from this config
  4. import this config into /dist/server/index.js a. any mentions of process.env.NEXTAUTH_URL will now also search for a url from this config

Future

This package needs extensive testing and should be made more dynamic. Setting the baseUrl in the options of [...nextauth].js should be possible.