Registry / data / analytics-utils

analytics-utils

library1.1.1jsnpmunverified

analytics-utils is a lightweight utility library providing common data manipulation functions specifically designed to support the 'analytics' module ecosystem. Currently at version 1.1.1, this package does not follow a strict time-based release cadence but typically releases new versions in conjunction with updates or new features in the primary 'analytics' library. Its key differentiators include a focused API tailored for analytics payload processing, often leveraging immutable data patterns, and first-class TypeScript support. It is not intended as a general-purpose utility library like Lodash or Ramda, but rather as a specialized toolkit for tasks such as deep property access, data cleaning, and transformation within an analytics context.

data

npm install analytics-utils

github ↗package ↗

INSTALL

IMPORT

SIG · ANALYTICS-UTILS

analytics-utils

datajavascriptv1.1.1

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

get

✓ import { get } from 'analytics-utils'

✗ const get = require('analytics-utils').get

While CommonJS `require` might work in Node.js, `analytics-utils` is primarily designed for modern JavaScript environments using ESM. For deep object access, `get` is a common utility.

set

✓ import { set } from 'analytics-utils'

✗ import set from 'analytics-utils'

Most utilities are named exports. Attempting a default import for `set` will result in `undefined` or an error. This function is for setting deep properties immutably.

isPlainObject

✓ import { isPlainObject } from 'analytics-utils'

✗ import { isObject } from 'analytics-utils'

The library likely offers specific type-checking utilities like `isPlainObject` rather than a generic `isObject` to differentiate from arrays, functions, etc. Always check exact utility names.

Demonstrates importing and using common `analytics-utils` functions like `get`, `set`, and `isPlainObject` for manipulating analytics event data, showcasing deep property access, immutable updates, and type checking.

import { get, set, isPlainObject } from 'analytics-utils'; interface AnalyticsEvent { eventName: string; payload: Record<string, any>; context?: Record<string, any>; } const originalEvent: AnalyticsEvent = { eventName: 'UserLoggedIn', payload: { userId: 'abc-123', email: 'user@example.com', preferences: { theme: 'dark', notifications: true } }, context: { platform: 'web', device: 'desktop' } }; // Get a deep property const userTheme = get(originalEvent, 'payload.preferences.theme'); console.log('User Theme:', userTheme); // 'dark' // Set a deep property (immutably returns a new object) const updatedEvent = set(originalEvent, 'payload.preferences.notifications', false); console.log('Original notifications:', get(originalEvent, 'payload.preferences.notifications')); // true console.log('Updated notifications:', get(updatedEvent, 'payload.preferences.notifications')); // false // Check if a value is a plain object const isPayloadObject = isPlainObject(originalEvent.payload); console.log('Is payload a plain object?', isPayloadObject); // true const isUserThemeObject = isPlainObject(userTheme); console.log('Is userTheme a plain object?', isUserThemeObject); // false

Debug

Known issues

gotcha`set` and similar data manipulation functions in `analytics-utils` are designed to be immutable, returning a new object with the changes rather than modifying the original object in place. Failing to assign the return value will result in no change to your data.

fix

Always capture the return value of functions like `set`: `const newObject = set(originalObject, 'path', value);`

affects: >=1.0.0

breakingPrior to v1.0.0, some utility functions might have been directly available on a default export or required different import paths. As of v1.0.0, the package primarily uses named exports for individual utilities.

fix

Update your imports to use named exports: `import { utilityName } from 'analytics-utils';`. Review the specific utility function names as some might have been renamed for consistency.

affects: <1.0.0

gotchaThe `get` utility function, if a path does not exist, will return `undefined`. While this is standard, ensure your code explicitly handles `undefined` return values to prevent runtime errors when accessing properties of non-existent nested objects.

fix

Use nullish coalescing or optional chaining where appropriate: `const value = get(obj, 'path') ?? 'defaultValue';` or `const value = get(obj, 'path')?.someProp;`

affects: >=1.0.0

deprecatedOlder versions of the `analytics` module might have bundled some of these utilities directly. Relying on such implicit re-exports is deprecated. Always import utilities directly from `analytics-utils` for forward compatibility and clarity.

fix

Migrate any direct `analytics` module utility calls to explicit imports from `analytics-utils`: `import { utility } from 'analytics-utils';`

affects: <1.0.0

Errors

Common errors & fixes

TypeError: (0 , analytics_utils__WEBPACK_IMPORTED_MODULE_0__.get) is not a function

Attempting to call a named export (`get`) on a module that was incorrectly imported as a default export, or a CommonJS module being treated as an ESM module without proper interop.

fix

Ensure you are using named imports for individual utilities: `import { get } from 'analytics-utils';`

Property 'someUtil' does not exist on type 'typeof import("analytics-utils")'. Did you mean 'someOtherUtil'?

Attempting to import a utility function with an incorrect name or a function that no longer exists/was never part of the public API. TypeScript flags this at compile time.

fix

Consult the `analytics-utils` documentation or source code to verify the exact name of the utility function you intend to use. Most utilities are named exports.

Upgrade

Version history

1.1.1latest on npm

Audit

Dependencies

@types/dlvoptionalProvides type definitions for the 'dlv' package, which is likely used internally or re-exported for deep object value retrieval.

Agent activity

39 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/DavidWells/analytics ↗

packagehttps://www.npmjs.com/package/analytics-utils ↗