This library, `raptor-util`, is a collection of core utility functions designed for the RaptorJS framework, an end-to-end JavaScript toolkit initially developed by eBay for building adaptive modules and UI components. The package provides various common helpers, likely including object manipulation, type checking, and other foundational utilities to support the broader RaptorJS ecosystem. The current version is 3.2.0. However, the RaptorJS framework and its associated packages, including `raptor-util`, appear to be abandoned, with the last notable activity around 2017 and related npm packages last published around 2014-2015. It is no longer actively maintained or developed, making it unsuitable for new projects.
npm install raptor-utilVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates importing `extend`, `isObject`, and `forEach` utilities using CommonJS `require` and showcases their basic usage for object merging, type checking, and iteration.
Avoid using `raptor-util` for new projects. Consider modern, actively maintained utility libraries like Lodash, Ramda, or even native browser/Node.js APIs which have evolved significantly since this package's last update.
If absolutely necessary to use in a modern project, configure your bundler (e.g., Webpack, Rollup, Parcel) to handle CommonJS modules or use a CommonJS compatible Node.js environment. For browser usage, ensure it's bundled and polyfilled appropriately.
Create a `declarations.d.ts` file or similar in your project with `declare module 'raptor-util';` or more specific declarations for the functions you use. For example: `declare module 'raptor-util' { export function extend(...args: any[]): any; export function isObject(value: any): boolean; export function forEach(collection: any, iteratee: Function): void; }`This package is designed for CommonJS. You either need to run your code in a CommonJS environment or configure a bundler to handle CommonJS modules within an ESM project. Direct ESM `import` statements for `raptor-util` are unlikely to work without extensive build tooling.
Double-check the exact export names of the utility functions you intend to use. Without official documentation, this may require inspecting the package's source code if you truly need to use it. Many common utility functions have standard names, but this package's specific exports are not publicly documented.
No dependency data recorded yet.