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

@protomodule/instruments

v0.2.0

Published

Frontend instruments for webbrowser applications which follow protomodule compatible practices.

Downloads

67

Readme

⚛️ Protomodule | Instruments

for browser based JavaScript applications

NPM Version NPM Install Size NPM Downloads

Protomodule is a set of common practices which span from coding over CI/CD to production deployments. Every utility within Protomodule is able to provide core functionality as a standalone tool. All Protomodule utilities are interoperable to get the most out of your DevOps pipeline with minimum effort.

Instruments is the JavaScript module to integrate Protomodules principles into browser based applications.

🚨 This library is under heavy development. Be sure to check back for breaking changes in future releases.

Quick start guide

Install Protomodule | Instruments by running:

$ npm install --save @protomodule/instruments

Features

Type-safe environment variables

To access environment variables in a type-safe way create a singleton module with your specific environment schema:

./config.ts

import { fromWeb, requiredStr } from "@protomodule/instruments"

export const config = fromWeb({
  REACT_APP_API_URL: requiredStr(),
})

In any other part of your application when you need to access an environment variable use:

import { config } from "./config.ts"

console.log(config.REACT_APP_API_URL)

In addition to providing a typed configuration object Protomodule | Instruments also check the variables at runtime and will show an alert and ultimatly throw an error when trying to access an invalid configuration.

🖥 Setting environment variables locally

During development this is meant to be used in conjunction with react-script. Therefore you have direct access to your local environment variables.

🌍 Setting environment variables in production

This library follows the Protomodule practice of loading environment variables into window.env in the browser.

This can be achieved by adding a snippet to your HTML's head section:

<!DOCTYPE html>
   <html lang="en">
   <head>
      <meta charset="utf-8" />
      <script src="%PUBLIC_URL%/env.js"></script>
 ...

env.js file should serve to following content:

window.env = {
  REACT_APP_API_URL: "https://...",
};

If you use the Protomodule related build tools, this file may be generated automatically when configured.

Credits

License

This project is licensed under the terms of the MIT license. See the LICENSE file.

This project is in no way affiliated with Apple Inc or Google Inc. This project is open source under the MIT license, which means you have full access to the source code and can modify it to fit your own needs.