open-index/open-npm huggingface dataset:
npm package: @hdnax/genuix
Description: A personal design system — Gene + UI/UX = Genuix.
Latest version: 0.3.0

# Genuix

![Status](https://img.shields.io/badge/status-active-brightblue)
![Version](https://img.shields.io/badge/version-0.3.0--alpha-orange)
![License](https://img.shields.io/badge/license-MIT-green)

A personal design system with DNA in its name — **Gene** + **UI/UX** = **Genuix** (sounds like "genuine-x").

Also a place to document my findings of building a design system.

**Progress tracker**: [Design System Home](https://painted-jodhpur-6fe.notion.site/Design-System-Home-2e6aa8fcd08880cb94bbe70c80eb0fa1)

## Motivation

- Sharpen frontend skills — both logic and visual design.
- Learn how design systems are built and maintained.
- Explore UI/UX best practices hands-on.
- Build personal libraries to use across my projects.
npm package: @hdnax/nuclint
Description: Shared ESLint configuration.
Latest version: 0.9.1

# Nuclint

![Status](https://img.shields.io/badge/status-active-brightblue)
![Version](https://img.shields.io/badge/version-0.4.0--alpha-orange)
![License](https://img.shields.io/badge/license-MIT-green)

Shared ESLint configuration for the RNA monorepo.
npm package: @hdnax/stdx
Description: Shared useful utilities.
Latest version: 0.1.0

# Stdx

![Status](https://img.shields.io/badge/status-active-brightblue)
![Version](https://img.shields.io/badge/version-0.1.0--alpha-orange)
![License](https://img.shields.io/badge/license-MIT-green)

Shared useful utilities.
npm package: @hdnet/commitlint-config
Description: HDNET commitlint-config, implementing HSR-3
Author: HDNET
Latest version: 1.0.2

# HDNET commitlint-config

This packages defines the strict implementation of the HDNET Commit Message Guidelines
from the HDNET Standard Recommendations
([HSR-3](https://hdgroup.atlassian.net/wiki/spaces/OPS/pages/45940834/HSR-3+Git+Commit-Messages)) as npm package
using [commitlint](https://commitlint.js.org/)
through a [shareable config](https://commitlint.js.org/#/concepts-shareable-config).

## Getting started

1. Ideally, setup Node.js >= 20.

2. Install dependencies
```bash
$ npm i -D @commitlint/cli @hdnet/commitlint-config

For Node.js < 18:
$ npm i -D @commitlint/cli@17 @hdnet/commitlint-config@0

For Node.js < 20:
$ npm i -D @commitlint/cli@18 @hdnet/commitlint-config@0
```

3. Create commitlint config (i.e. `commitlint.config.mjs`) and extend from @hdnet/commitlint-config:
```javascript
export default {
    extends: '@hdnet',

    parserPreset: {
        parserOpts: {
            // replace "PROJECT-" with your issue prefix
            issuePrefixes: ['PROJECT-'],
        },
    },
}
```

4. Add commitlint to you git hook configuration (i.e. using [husky](https://commitlint.js.org/#/guides-local-setup?id=install-husky))


## Contribute

To setup current node version, you can use [nvm](https://github.com/nvm-sh/nvm)
(in this project a [.nvmrc](./.nvmrc) file is maintained).
npm package: @hdnet/list-update-hints
Description: Script to list custom hints to updatable dependencies
Author: HDNET
Latest version: 1.0.1

# HDNET list-update-hints

This npm package lists custom update hints to updatable npm packages in your repo.
In a custom `package.json.md` file you can define some information about updatable
dependencies. You can use it for i.e.

- information about updates that are not made too easily
- hints about steps to apply when updating a dependency
- notes to fixed package versions
- important notes about a custom update routine
- ...

The entries must appear after a title `Update Hints` and follow the syntax:

```markdown
- `<package>` some info about the update of the package @https://some-ticket-system/MYTICKET-1234
```

If you then run `hdnet-list-update-hints`, the script will list available updates using `npm outdated`
and join the in information hints you provided within a simple table.


## Getting started

1. Install the dependency in your repository
```bash
$ npm i -D @hdnet/list-update-hints
```

2. Create a package.json.md file and append a section called `Update Hints` with the following format at the end of the file:
```markdown
# Update Hints
- `nuxt` v2 is EOL - plan the migration in the next sprints!
- `eslint` run tests for custom plugins before updating! @https://some-ticket-system/MYTICKET-1234
- `stylelint` we have to update to at least node@18.12.0 to update to stylelint@16
- `hdnet-list-update-hints` issue feature is missing @https://github.com/HDNET/list-update-hints/issues/1
```

3. Run script
```bash
$ hdnet-list-update-hints

# use option --without-hints to display updatable packages only
$ hdnet-list-update-hints --without-hints
```


## Contribute

To setup current node version, you can use [nvm](https://github.com/nvm-sh/nvm)
(in this project a [.nvmrc](./.nvmrc) file is maintained).
npm package: @hdnet/prettier-config
Description: HDNET prettier-config, implementing HSR-15
Author: HDNET
Latest version: 2.0.5

# HDNET prettier-config

This packages defines the strict implementation of the HDNET Code Formatting Guidelines
from the HDNET Standard Recommendations
([HSR-15](https://wiki.hdnet.de/display/OPS/HSR-15%3A+Code-Formatierung)) as npm package
using [prettier](https://prettier.io)
through a [shareable config](https://prettier.io/docs/en/configuration.html#sharing-configurations).

## Getting started

1. Install dependencies

```bash
$ npm i -D prettier @hdnet/prettier-config
```

2. Create your prettier config file (i.e. `prettier.config.js`) and extend from @hdnet/prettier-config:

```javascript
import hdnetPrettierConfig from '@hdnet/prettier-config'

export default {
  ...hdnetPrettierConfig,
}
```

## Notes

We explicitely parse .json files as JSON which differs from the behavior within prettier itself where certain files are assigned to JSON5 or JSONC.

## Contribute

To setup current node version, you can use [nvm](https://github.com/nvm-sh/nvm)
(in this project a [.nvmrc](./.nvmrc) file is maintained).
npm package: @hdnet/semantic-release-config
Description: HDNET semantic-release config, implementing HSR-20
Author: HDNET
Latest version: 3.3.3

# HDNET semantic-release-config

This packages defines the strict implementation of the HDNET Semantic Release Workflow
from the HDNET Standard Recommendations
([HSR-20](https://hdgroup.atlassian.net/wiki/spaces/OPS/pages/182386689/HSR-20+Releaseworkflow+mit+semantic-release))
as npm package
using [semantic-release](https://github.com/semantic-release/semantic-release)
through a
[shareable config](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/shareable-configurations.md).

## Getting started

1. Make sure you use Node.js >= 20.

2. Install dependencies
```bash
$ npm i -D semantic-release @hdnet/semantic-release-config
```

3. Create a semantic-release config (i.e. `release.config.mjs`) and extend from @hdnet/semantic-release-config:
```javascript
export default {
    extends: '@hdnet/semantic-release-config',
}
```

4. Add semantic-release to your CI workflow.


## Features

* supports composer through `@iwavesmedia/semantic-release-composer` plugin
* allows overwriting `issueUrlFormat` through the env `ISSUE_URL_FORMAT`
* allows setting `issuePrefixes` (default: `#`) through the env `ISSUE_PREFIX`
* allows publishing to a package repository when `publish` is set to `true` through `PUBLISH`
* allows customizing the `next`-channel branch name through the env `NEXT_BRANCH`

## Contribute

To setup the correct node version, use tools like [nvm](https://github.com/nvm-sh/nvm) or [mise](https://github.com/jdx/mise). This project maintains an [.nvmrc](./.nvmrc).

## Publishing

A new version will automatically be published upon comitting to the `main` branch and pushing to the [bitbucket repository](https://bitbucket.org/hdnet/semantic-release-config/src/main/).
npm package: @hdnet/stylelint-config
Description: HDNET stylelint-config
Author: HDNET
Latest version: 1.0.2

# HDNET stylelint-config

This packages defines the HDNET [stylelint](https://stylelint.io) configuration
through a [shared config](https://stylelint.io/user-guide/get-started/#using-a-community-shared-config). 

## Getting started

1. Make sure you setup node >= 14

2. Install dependencies
```bash
$ npm i -D stylelint @hdnet/stylelint-config
```

3. Create stylelint config (i.e. `stylelint.config.js`) and extend from @hdnet/stylelint-config:
```javascript
module.exports = {
    "extends": "@hdnet/stylelint-config"
}
```

## Contribute

To setup current node version, you can use [nvm](https://github.com/nvm-sh/nvm) 
(in this project a [.nvmrc](./.nvmrc) file is maintained).