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 🙏

© 2026 – Pkg Stats / Ryan Hefner

tabletcommand-sync-settings

v2.2.19

Published

Tablet Command Sync Settings

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

bamse16bamse16goemangoemanartarmstrongartarmstrong

Keywords

Readme

tabletcommand-sync-settings

A TypeScript library for managing and formatting user settings in the Tablet Command ecosystem. This package centralizes the logic for computing user-specific settings by merging department configurations, user preferences, agency settings, and environmental configurations.

Development

Building

npm run build

Testing

npm test

Linting

npm run lint

Package Maintenance

Upgrading Dependencies

Before publishing a new version, follow these steps to keep dependencies up to date:

1. Install npm-check-updates (one-time setup)

npm i -g npm-check-updates

2. Update Minor Versions

Run this command in the same folder where package.json is located:

npx ncu -i --target minor

Review and select packages that are safe to update, such as:

  • Development tools: cspell, eslint, mocha, chai, @types/*
  • Internal packages: tabletcommand-backend-models (e.g., 7.4.15 → 7.4.34)

3. Check for Major Version Updates

Run without the --target minor flag to see all available upgrades:

npx ncu -i

Evaluate each major version upgrade carefully:

Examples of Safe to Upgrade
  • uuid: Compatible upgrades from v9 → v10 → v11 → v12 → latest
  • mocha/chai: Generally compatible across versions
  • Development dependencies: Usually safe to upgrade
Proceed with Caution
  • @types/node: Match your Node.js environment version
    • Example: If running Node.js 22.x, use @types/node ^22.x.x, NOT ^25.x.x
  • @esri/@arcgis packages: Do NOT upgrade without testing - breaking changes common
  • redis packages: Incompatible changes between major versions
    • Note: Current test mocking libraries don't support the latest Node.js Redis package

4. Track Outdated Dependencies

For packages that cannot be safely upgraded:

  • Create a story to track the outdated dependency
  • Document why it can't be upgraded
  • Note possible solutions or blockers

5. Verify Security Alerts

After updating and pushing changes, verify that Dependabot alerts are cleared:

https://github.com/TabletCommand/tabletcommand-sync-settings/security/dependabot

Best Practices

  • Always test after upgrading dependencies
  • Review changelogs for major version bumps
  • Run the full test suite before publishing
  • Keep @types/node aligned with your Node.js version
  • Document any upgrade blockers or compatibility issues

Repository

https://github.com/TabletCommand/tabletcommand-sync-settings