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

@builtwithjavascript/server-side-config

v1.0.7

Published

Hook useServerSideConfig to more easily load json files with strongly typed configuration models for use in Nuxt, Next, Node, etc on the server side

Downloads

7

Readme

server-side-config

Hook useServerSideConfig to more easily load json files with strongly typed configuration models for use in Nuxt, Next, Node, etc on the server side

@builtwithjavascript/server-side-config

Hook useServerSideConfig to more easily load json files with strongly typed configuration models for use in Nuxt, Next, Node, etc on the server side

npm version

code base

TypeScript

Description

Contains hooks:

  • useServerSideConfig

How to use

IMPORTANT: this node should not be installed globally as it will not work that way

install:

npm i -D @builtwithjavascript/server-side-config

consume:

// create the TypeScript interface that will define the structure of your config file
// and save it under your model or other directory ('./your-path-to-your-iconfig-model'):
// for example: 
interface IConfig {
  name: string,
  marketing: {
    title: string
    hero: string
  },
  meta: {
    title: string
    description: string
  }
}

// create a json file named app1.json that adheres to the above interface and save it 
// under a directory on your project (by default the hook will look into ./config/config-files/):
{
  "name": "for-unit-tests-only",
  "marketing": {
    "title": "For unit-tests only",
    "hero": "An example for the config file."
  },
  "meta": {
    "title":  "For unit-tests only",
    "description": "An example for the config file."
  }
}

// in the code where you need to consume the server-side config file (i.e. in Nuxt this would be in nuxt.config.ts), import a reference to the useServerSideConfig hook and your IConfig interface:
import { useServerSideConfig } from '@/server-side-config/'
import type { IConfig } from './your-path-to-your-iconfig-model'

// then load the server-side config file using the useServerSideConfig and passing the app key, in this case 'app1'
const instance = useServerSideConfig<IConfig>('app1')

// Note: usually you will read the value of 'app1' from an environment variable, i.e.
const instance = useServerSideConfig<IConfig>(process.env.SITE_KEY)

// the default base directory for your json files is /config/config-files/ 
// but you could optionally specify a different path by passing this as the second arugment:
const configFilesDirectoryPath = `../my-config-files/`
const instance = useServerSideConfig<IConfig>(process.env.SITE_KEY, configFilesDirectoryPath)

Dev dependencies:

@types/jest @types/node jsdom prettier ts-node typescript vite vitest