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

node-scc-config

v1.2.1

Published

Configuring a Node.js application based on Spring Cloud Config

Downloads

912

Readme

Configure your Node.js applications using Spring Cloud Config

Build Status Download Status

Benefits

  • Server and client data decryption

Installation

npm install node-scc-config
yarn add node-scc-config

Usage

  1. Create a client-side pointer to the Spring Cloud Config service

    const client = new SpringCloudConfigClient('your spring cloud config endpoint address...');
  2. Configuring the client before calling

    client
        .beforeLoad(s => ({
            your request options...
        }))
  3. Configuring the client after the call

    Chipher marker defaults to '{cipher}'

  • Chipher marker
    client
        .afterLoad(d => d
            .setChipherMarker('your chipher marker...')
  • Data replacer by templates

    Example: { ['{HOST}']: 'test', ['{SERVICE_NAME}']: 'app-service' }

    client
        .afterLoad(d => d
            .setReplacer('your template...')
  • Data decryption
    • client
      client
          .afterLoad(d => d
              .setDecryptor(new AesDecryptor('your secret key or password...')))
    • server
      client
          .afterLoad(d => d
              .setDecryptor(new ServiceDecryptor('your decryption endpoint address...')))
  • Source preparation
    • Merge source

      Default implementation if no function is specified

      client
          .afterLoad(d => d
              .setMergeSource<AppServiceApiConfig>((configuration?: TConfiguration<AppServiceApiConfig>) => {
                  your code to merge source...
              }))
    • Prepare source

      Default implementation if no function is specified

      client
          .afterLoad(d => d
              .setPrepareSource<AppServiceApiConfig>((source: Record<string, any>) => {
                  your code to prepare source...
              }))
  1. Call loading the configuration

    await client.load();
  2. Using the loaded configuration

    type AppServiceApiConfig = {
        logLevel: string;
        options: {
            service: {
                url: string;
                login: string;
                password: string;
            };
        };
        testOptions: {
            url: string;
        };
    };
    
    const config = getConfiguration<AppServiceApiConfig>();