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

vymo-config-stub-js

v1.3.6

Published

This stub is for polling config service to fetch, update and cache the config locally to the service

Downloads

24

Readme

Methods exposed

There are two major functions exposed for initializing configuration fetch and polling. Apart from them there were other functions like getClientsIncludingDisabled , getClient, getClientGlobalConfig which are self explanatory.

Fetch first time configurations

context = {
   URL: "Config service url to be used for polling"
}
.init(context)

Fetching specific client configurations

context = {
   URL: "Config service url to be used for polling",
   client: [] //"Array of clients which should be loaded"
}
.init(context)

Poll incremental configurations

context = {
   URL: "Config service url to be used for polling",
   TIMEOUT_IN_SECONDS: "Interval of polling"
   client: [] //"Array of clients which should be loaded"
}
.poll(context)

Incase of standalone tasks, only first time fetch will be required, in such cases poll can be disabled. By default poll is set to true.

context = {
   URL: "Config service url to be used for polling",
   TIMEOUT_IN_SECONDS: "Interval of polling"
   client: ["client"],
   poll: false
}
.poll(context)

Also, JS client provides ability to listen to any configuration updates inmemory.

  • CLIENT_UPDATED - Gets called whenever any client update happens

  • GLOBAL_UPDATED - Gets called whenever any global update happens

Building the package

  1. nvm use 12

  2. npm publish

  3. npm pack if error comes (npm ERR! 404 Not Found - PUT https://registry.npmjs.org/vymo-config-stub-js - Not found) do npm login and create login cred for Example: $ npm login

    Username: prudhvitejapotnuru

    Password: Email: (this IS public) [email protected] npm notice Please check your email for a one-time password (OTP) Enter one-time password from your authenticator app: Logged in as prudhvitejapotnuru on https://registry.npmjs.org/.

  4. Make sure that the version is changed every time of retry.

  5. then do npm publish and npm pack

  6. a file will be present in same path vymo-config-stub-js-{version}.tgz

  7. Copy this tgz inside the resources/ of {userService}(ex lms) directory

  8. Increment the version in the {userService}(ex lms) package.json

  9. Go to lms and update the version in the npm-shrinkwrap.json

  10. Commit the npm-shrinkwrap.json file else npm will not install the newer version even though you update version in the package.json