# @opndev/util

> Utility functions for OPN Development

Latest version **0.0.11** (published 2026-02-15) · MIT license · 0 weekly downloads

## Install

```sh
npm install @opndev/util
pnpm add @opndev/util
yarn add @opndev/util
bun add @opndev/util
```

## Health

**Score 50/100 (C)** — status: stable.

Positive: esm support; no vulnerabilities.

Warnings: low downloads; no types; pre 1.0.

## Facts

| | |
|---|---|
| Version | 0.0.11 |
| Published | 2026-02-15 |
| First published | 2020-05-14 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | ESM |
| Dependencies | 0 |
| Unpacked size | 10.3 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | Wesley Schwengle |
| Maintainers | waterkip |
| Keywords | utility |

## Links

- npm: https://www.npmjs.com/package/@opndev/util
- Repository: https://gitlab.com/opndev/javascript/opndev-js-util
- Homepage: https://opndev.gitlab.io/javascript/opndev-js-util/
- Issues: https://gitlab.com/opndev/javascript/opndev-js-util/-/issues
- npm.io page: https://npm.io/package/@opndev/util

## Alternatives

- [lodash.assign](https://npm.io/package/lodash.assign.md) — 2.3M weekly downloads
- [lodash.chunk](https://npm.io/package/lodash.chunk.md) — 1.8M weekly downloads
- [react-native-ios-utilities](https://npm.io/package/react-native-ios-utilities.md) — 138.5K weekly downloads
- [@technically/lodash](https://npm.io/package/@technically/lodash.md) — 50.9K weekly downloads
- [@fluid-topics/ft-icon](https://npm.io/package/@fluid-topics/ft-icon.md) — 20.6K weekly downloads

## Recent versions

- 0.0.11 (latest) — 2026-02-15
- 0.0.10 — 2026-02-15
- 0.0.9 — 2026-02-15
- 0.0.8 — 2024-06-04
- 0.0.7 — 2024-01-19
- 0.0.6 — 2023-09-03
- 0.0.5 — 2023-08-27
- 0.0.4 — 2023-08-27
- 0.0.3 — 2021-11-12
- 0.0.2 — 2020-05-15
- 0.0.1 — 2020-05-14

## README

<!--
SPDX-FileCopyrightText: 2020-2024 Wesley Schwengle <wesley@opndev.io>

SPDX-License-Identifier: MIT
-->

# Welcome to @opndev/util

This is a utility function package that tries to solve issues by keeping things
DRY. It is an ESM package.

[If you want to know more, have a look at our documenation](https://opndev.gitlab.io/javascript/opndev-js-util/)

## Development

Try to keep functions small and try not to depend on any outside functions. We
aim to keep the dependency graph as small as possible. The use of `esm` is
welcomed and writing tests is encouraged.

### jsdoc

You can build the documentation by running `npm run jsdoc`.

### eslint

The ES Linting profile is flexible and does not try to enforce much. There is
more than one way to do it ([TIMTOWTDI](https://en.wikipedia.org/wiki/There%27s_more_than_one_way_to_do_it)).

Try to stay constistent, but forcing a programming style upon others is bad.

### gitignore

Please educate yourself and use a global gitignore file. Somes files will
always be there. I'm looking at you `node_modules`.

### The lockfiles
You'll also see that `package-lock.json` and/or `yarn.lock` are ignored. I
strongly believe that pinning packages lead to bit rot, as you never update
packages. When a downstream module breaks its API you should know and update
your code accordingly. The same goes for possible upstream modules. If you want
a specific version, pin it to that version, otherwise use the latest and
greatest when possible.

### Code of conduct

There is none, stay human, communicate and accept that some people have
different opinions.

### Pull requests

I'm happy to accept pull requests, just make sure your change has tests.
Add a good commit message and commit with a sign-off `git commit -s`.

A good commit message isn't just `issue(feat): added foo to bar` but also
explain the why in the commit.

---
_Source: https://npm.io/package/@opndev/util · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._