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

@visuanex/core-utils

v1.0.5

Published

Utils for typescript/javascript develompment

Downloads

3

Readme

base-ts-utils

Install

npm install --save @visuanex/core-utils

Usage

Env

Enviromnet contains utils for code environment. To start you can import the Utility class by adding the following line to your code

import {Env} from '@visuanex/core-utils'

Env.isProduction(): boolean

Checks if the environment is in production mode (NODE_ENV=production), returns true if is set to production

Env.isDevelopment(): boolean

Checks if the environment is in development mode (NODE_ENV=development), returns true if is set to development

Env.isTest(): boolean

Checks if the environment is in test mode (NODE_ENV=test), returns true if is set to test

Env.getEnvironment(): string

Get the current environment string (already trimed)

Env.prefix(str: string): string

Add environment as prefix to the input

process.env.NODE_ENV = 'development'
Env.prefix("test") // development_test
Env.prefix("test1") // development_test1

Env.postfix(str: string): string

Add environment as postfix to the input

process.env.NODE_ENV = 'development'
Env.prefix("test") // test_development
Env.prefix("test1") // test1_development

Env.config

The configuration can accept a few parameters

key | type | default | Description -------|-------|---------|------------- env_key | string | "NODE_ENV" | the environment variable name (that contains the environment value) default_env | string | "development" | the environment value

Example

# .env

MY_ENV=production
Env.isDeveloment() // true because default variable is "NODE_ENV" and default value is "development"
Env.config.default_env = 'test'
Env.isDeveloment() // false because default variable is "NODE_ENV" and default value is now "test"
Env.isTest() // true because default variable is "NODE_ENV" and default value is still "test"
Env.config.env_key = 'MY_ENV'
Env.isTest() // false because default variable is now "MY_ENV" and value was set to "production"
Env.isProduction() // true because default variable is now "MY_ENV" and value was set to "production"

Types

The package also contains a list of satndard types usefull

export type Callback<T = any> = (err?: Error|null|undefined, data?: T) => void