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

snget

v1.0.4

Published

A utility to export & import ServiceNow records from one instance to another.

Downloads

5

Readme

snGet

A utility to export & import ServiceNow records from one instance to another.

Setup from ZIP file

  1. Download ZIP file
  2. Extract ZIP
  3. Open snget folder in VS Code
  4. npm i in integrated Terminal
  5. Rename or copy .env.example to .env
  6. Update the target and source variables as needed
  7. Run in the terminal node app.js
  8. Enter table: incident
  9. Enter encoded query: sys_id=A1234567890
  10. Check the target instance to make sure the records have inserted or updated based on your encoded query

Setup from GitHub

  1. Clone repo
  2. Browse to the repo directory in the terminal cd snget
  3. Install dotenv dependency using npm i
  4. Rename or copy .env.example to .env
  5. Update the target and source variables as needed
  6. Run in the terminal node app.js
  7. Enter table: incident
  8. Enter encoded query: sys_id=A1234567890
  9. Check the target instance to make sure the records have inserted or updated based on your encoded query

Setup from NPM

  1. npm i snget
  2. Move the snget folder out of node_modules and into the project root directory
  3. Move the node_modules folder into the snget folder
  4. Change to the snget directory in terminal
  5. Rename or copy .env.example to .env
  6. Update the target and source variables as needed
  7. Run in the terminal node app.js
  8. Enter table: incident
  9. Enter encoded query: sys_id=A1234567890
  10. Check the target instance to make sure the records have inserted or updated based on your encoded query

This is temporary until I publish a better solution for NPM