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

@eluvio/elv-js-helpers

v6.3.3

Published

A collection of Javascript helper functions used by several Eluvio libraries.

Downloads

111

Readme

elv-js-helpers

A collection of Javascript helper functions used by several Eluvio libraries.

THIS LIBRARY IS CURRENTLY IN PRE-RELEASE: FUNCTION NAMES AND SIGNATURES ARE STILL IN FLUX.

API Documentation

https://eluv-io.github.io/elv-js-helpers/api.html

Installation

Install from NPM:

npm install --save @eluvio/elv-js-helpers

Usage

It is possible to import individual items or the entire library, depending on whether code size is a concern.

Entire library (CommonJS)

// namespace entire suite to a const
const H = require('@eluvio/elv-js-helpers')

console.log(H.Datetime.now())

// create references to particular items in order to avoid needing to use H.Category prefix
const { etaDurStr, etaTimeStr } = H.Datetime
const {_boundLowerErrMsg} = H.ModelAssertion

// Get reference to 1 category (note that this will still wind up incuding the entire package)
const { Datetime } = require('@eluvio/elv-js-helpers')
console.log(Datetime.now())

Entire library (JS Modules)

// namespace entire suite to H
import H from '@eluvio/elv-js-helpers'

// create references to particular items in order to avoid needing to use H. prefix
const { etaDurStr, etaTimeStr } = H.Datetime
const {_boundLowerErrMsg} = H.ModelAssertion

// Note that the following syntax still causes entire library to be bundled into your project
import { Datetime }  from '@eluvio/elv-js-helpers'

Individual items (CommonJS)

Importing individual items will minimize code size.

// require in each item directly
const etaDurStr = require('@eluvio/elv-js-helpers/Datetime/etaDurStr')
const etaTimeStr = require('@eluvio/elv-js-helpers/Datetime/etaTimeStr')
const _boundLowerErrMsg = require('@eluvio/elv-js-helpers/ModelAssertion/_boundLowerErrMsg')

Individual items (JS Modules)

// import in each item directly
import etaDurStr from '@eluvio/elv-js-helpers/Datetime/etaDurStr'
import etaTimeStr from '@eluvio/elv-js-helpers/Datetime/etaTimeStr'
import _boundLowerErrMsg from '@eluvio/elv-js-helpers/ModelAssertion/_boundLowerErrMsg'

Entire library (browser)

Although not recommended, it is also possible to import the entire library directly into a browser via a <script> tag pointing to a copy of either dist/elv-js-helpers.js or dist/elv-js-helpers.min.js. This will create a variable named ElvJsHelpers in the global namespace. There is no support for importing individual items via a <script> tag. (It is expected that browser apps would be built using a bundling tool like Webpack/Rollup/Parcel)

<!-- Import entire library as ElvJsHelper -->
<script src="elv-js-helpers.js"></script>
<script type="application/javascript">
    console.log('System locale is: ' + ElvJsHelpers.Datetime.sysLocale())
    console.log('_boundLowerErrMsg(0,true)= "' + ElvJsHelpers.ModelAssertion._boundLowerErrMsg(0,true) + '"')
</script>

Conventions

Source Files (src/CATEGORY/*.js)

  • Each function (or exported constant) has its own source file.
  • Each source file exports exactly 1 item.
  • Files have the same case-sensitive name as the function or constant it defines (with .js extension added)
  • Files are stored in subdirectories of src/ according to category (1 category per subdirectory)

Naming / Capitalization

Abbreviations

  • Names tend to err on the side of not abbreviating, prioritizing clarity over brevity:
    • conditionalCheck not condlChk (function)
    • sysTimezone not sysTZ (function)
  • When an item name would be cumbersome or excessively long otherwise, abbreviations and/or acronyms are used for words where the meaning remains reasonably clear and obvious:
    • assertPropMaxGTEMin not assertPropertyMaximumGreaterThanOrEqualToMinimum (function)
    • defNonEmptyArrModel not defineNonEmptyArrayModel (function)
    • RE_UTC_TIMESTAMP not REGEXP_UNIVERSAL_TIME_COORDINATED_TIMESTAMP (constant)
  • A few abbreviations stretch the "reasonably clear and obvious" condition:
    • ADT not AlgebraicDataType (category)
    • resultToPOJO not resultToPlainOldJavascriptObject (function)

Capitalization (general)

  • Compound words that are widely treated as single words do not capitalize the second word:
    • Datetime not DateTime (category)
    • sysTimezone not sysTimeZone (function)
    • RE_UTC_TIMESTAMP not RE_UTC_TIME_STAMP (constant)
  • Acronyms are kept all the same case, either upper or lower depending on kind of item and position within name:
    • ADT not Adt (category)
    • parseUTCStr not parseUtcStr (function)
    • utcStrToDate not uTCStrToDate (function)
    • etaDurStr not eTADurStr (function)
  • For greater legibility, the prefix "non" is treated as a word:
    • NonBlankStrModel not NonblankStrModel (model)
    • wrapNonArray not wrapNonarray (function)

Capitalization (by item type)

  • ADTs: PascalCase (List, Ok)
  • Categories: PascalCase (ModelAssertion, ModelFactory)
  • Constants: UPPER_SNAKE_CASE (RE_UTC_TIMESTAMP)
    • Regular expression names start with "RE_"
  • Models: PascalCase (NonBlankStrModel)
    • Model names always end with "Model"
  • Functions: camelCase (mapWithIndex, resultUnwrap)
    • Note that ADTs and Models are actually functions but are named using PascalCase because they are used more like classes.
    • ModelFactory names always start with "def" and end with "Model" (defArrModel, defObjModel)

Private Items

  • Have names beginning with underscore (_boundLowerErrMsg)
  • Are not truly private, they are available for use but are filtered from the documentation page unless Show private is checked.
  • Contain internal code shared by more than one function but considered too specialized to be useful outside the package