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

enforce-constants

v0.1.2

Published

Enforce constants to be defined before access and disallow redefining them after creation.

Downloads

4

Readme

EnforceConstants

Ensure that the constants you initially define will always be the constants you access.

This is a simple object wrapper that utilizes a Proxy to make sure that elements being accessed have been previously defined and that the object is not changing. Please note that this is not intended to securely enforce that the object is 100% identical to the original object. There are always new and exciting/dangerous ways to modify objects in JavaScript. Rather, this is meant as a help for developers to raise errors early in development and help avoid typos/accessing keys that they think are defined, etc.

Usage:

  const enforcedConstants = require('enforced-constants');

  const config = {
    appName: 'test application',
    docxMimeType: 'application/vnd.openxmlformats-officedocument.wordprocessingml.document'
  };

  module.exports = enforcedConstants(config, 'app config');

The first argument is the object to "freeze", the second is an optional name so that log messages can be more helpful in explaining what object the bad operation was performed against.

After enforcing the constant access of an object, you can read any of those properties, but you cannot write new properties, update existing ones, or delete properties. It is set against future modification.

I've found this approach helpful in applications that take large number of ENV vars, that interact with a 3rd party API that has field names differing from the code conventions the project uses, or really anywhere I would normally reach for an "Enum" type object.