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

@datawheel/bespoke

v0.5.0

Published

Content management system for creating automated data reports

Downloads

288

Readme

Reports

EnvVars

# Bespoke
REPORTS_DB_CONNECTION="postgres://user:@localhost:5432/database"
REPORTS_LOGGING=true
NEXT_PUBLIC_REPORTS_LOCALE_DEFAULT="en"
NEXT_PUBLIC_REPORTS_LOCALES="en,es"
REPORTS_BASE_URL="http://localhost:3000"

# Images
NEXT_PUBLIC_IMAGE_SPLASH_WIDTH=1400
NEXT_PUBLIC_IMAGE_THUMB_WIDTH=400

# Providers
NEXT_PUBLIC_IMAGE_PROVIDERS="upload,local,flickr,unsplash,adobe"
FLICKR_API_KEY="xxxx"
UNSPLASH_API_KEY="xxxx"
# unused ADOBE_STOCK_API_KEY="xxxx"
# unused ADOBE_STOCK_API_SECRET="xxxx"
# unused ADOBE_MANAGEMENT_API_KEY="xxxx"
# unused ADOBE_MANAGEMENT_API_SECRET="xxxx"

# Auth
AUTH0_SECRET="xxxxxxxxxxxxxxxxxxxxxxxxx"
AUTH0_BASE_URL="http://localhost:3000"
AUTH0_ISSUER_BASE_URL="https://xxxxxxx.auth0.com"
AUTH0_CLIENT_ID="xxxxxxxxxxx"
AUTH0_CLIENT_SECRET="xxxxxxxxxxx"

# Timeout
NEXT_PUBLIC_REPORTS_API_FETCH_TIMEOUT=100000

Environmental variables into Bespoke Report scope

Just add this in your nextjs.config.js

publicRuntimeConfig: {
  // Define your public environment variables for bespoke here
  bespoke_report_env_vars: {
      API: process.env.NEXT_PUBLIC_API || "N/A"
      WHATEVER: "hello"
  },
  // ...
},

And is gonna be offered as ENV_API and ENV_WHATEVER in the list of variables in the profile.