open-index/open-npm huggingface dataset:
npm package: @internetderdinge/api
Description: Shared OpenIoT API modules
Latest version: 1.229.26

# @wirewire/openiot-api

Shared OpenIoT API modules used by IoT hardware. This package provides prebuilt Express routers and shared middleware/models for OpenIoT-related features.

## Requirements

- Node.js >= 24
- Yarn (workspace dependency management)

## Install (workspace)

From the repo root:

- `yarn install`

## Build

From the repo root:

- `yarn --cwd packages/openiot-api build`

## Lint

From the repo root:

- `yarn --cwd packages/openiot-api lint`

## Usage

This package is ESM (`"type": "module"`). Import the routers and mount them in an Express app:

- `usersRoute`
- `accountsRoute`
- `organizationsRoute`
- `devicesRoute`
- `devicesNotificationsRoute`
- `pdfRoute`
- `tokensRoute`

Example:

- `import { usersRoute } from "@wirewire/openiot-api";`
- `app.use("/users", usersRoute);`

## Source layout

- `src/*`: Routers, middleware, models, validation, utils
- `src/index.ts`: Public exports

## Notes

- This is a private workspace package and is not published publicly.
npm package: @internethic/oparedo-ui
Description: VueJS Components
Latest version: 0.1.7

## OPAREDO VUEJS UI (@internethic/oparedo-ui)

[![Netlify Status](https://api.netlify.com/api/v1/badges/b9fb079f-4541-417e-a042-ad8da3b324e9/deploy-status)](https://app.netlify.com/sites/oparedo-ui/deploys)

Storybook available here : https://oparedo-ui.netlify.com/

Build is automatically triggered by netlify everytime a changed is pushed to the master branch.

#

### Install

```
npm install @internethic/oparedo-ui
```

### Usage

```
import Vue from 'vue'
import OparedoUI from '@internethic/oparedo-ui'
import '@internethic/oparedo-ui/dist/oparedo-ui.css'

Vue.use(OparedoUI)
```

#

### How to add your component

1. Create a git branch for your component
2. Create a folder named with your component name in CamelCase
3. Add your vue component file in CamelCase
4. Create a story for your component
5. Register your component in rollup listing ``src/index.js`` file
6. Build the components index file with rollup ``npm run build``
7. Commit your component branch
8. Ask for a merge request on master assigned to a frontend dev

### How to publish a new version of the package

1. Update package version in package.json
2. run "npm publish" (@TODO prepublish linting & testing)

### Commit types

- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
- docs: Documentation only changes
- feat: A new feature
- fix: A bug fix
- perf: A code change that improves performance
- refactor: A code change that neither fixes a bug nor adds a feature
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- test: Adding missing tests or correcting existing tests

TODO
- [ ] Add Storybook Snapshots
- [ ] CI for rollup build