open-index/open-npm huggingface dataset:
npm package: @serviceup/eslint-plugin-enforce-use-client
Description: ESLint plugin to enforce 'use client' directive in Next.js React components
Author: ServiceUp
Latest version: 1.0.0

# eslint-plugin-enforce-use-client

An ESLint plugin to ensure proper usage of the `'use client'` directive in Next.js React components.

## Description

In Next.js applications using the App Router, components that use client-side features (React hooks, browser APIs, event handlers) must include the `'use client'` directive at the top of the file. This plugin helps enforce this requirement by:

1. Requiring the `'use client'` directive in files with client-side features
2. Warning about unnecessary `'use client'` directives in files without client-side features

## Installation

```bash
npm install --save-dev @serviceup/eslint-plugin-enforce-use-client
# or
yarn add --dev @serviceup/eslint-plugin-enforce-use-client
# or
pnpm add --save-dev @serviceup/eslint-plugin-enforce-use-client
```

## Usage

Add to your ESLint configuration:

```javascript
// .eslintrc.js
module.exports = {
  plugins: ['@serviceup/enforce-use-client'],
  extends: [
    'plugin:@serviceup/enforce-use-client/recommended'
  ]
};
```

## Rules

This plugin provides two rules:

### enforce-use-client

Enforces that React component files using client-side features include the `'use client'` directive at the top.

Features detected:
- React hooks (functions starting with "use")
- Browser APIs (window, document, navigator, localStorage, sessionStorage)
- JSX event handlers (onClick, onChange, etc.)
- JSX elements presence

This rule is auto-fixable and will add the directive when needed.

### warn-unnecessary-use-client

Warns when the `'use client'` directive is used unnecessarily in files without any client-side features.

This rule is auto-fixable and will remove the directive when it's not needed.

## Configuration

Both rules automatically skip test files (files with names containing `.test.` or `.spec.`).

## Requirements

- ESLint 8.0.0 or higher
- Next.js 13.4.0 or higher (with App Router)

## License

MIT

## Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

## Development

### Running Tests

After cloning the repository and installing dependencies:

```bash
npm install
npm test
```

The tests verify that both rules correctly identify valid and invalid usage of the `'use client'` directive.
npm package: @serviceup/prisma-generator-class-validator
Description: Prisma 2+ generator to emit typescript models of your database with class validator
Latest version: 6.6.1

# Prisma Class Validator Generator

Automatically generate typescript models of your database with class validator validations ready, from your [Prisma](https://github.com/prisma/prisma) Schema. Updates every time `npx prisma generate` runs.

## Table of Contents

- [Supported Prisma Versions](#supported-prisma-versions)
- [Installation](#installing)
- [Usage](#usage)
- [Additional Options](#additional-options)
- [Development](#development)
- [Running Tests](#running-tests)

## Installation

```bash
 npm install prisma-generator-class-validator
```

# Usage

1- Add the generator to your Prisma schema

```prisma
generator class_validator {
  provider = "prisma-generator-class-validator"
}
```

3- Running `npx prisma generate` for the following schema.prisma

```prisma
model User {
  id    Int     @id @default(autoincrement())
  email String  @unique
  name  String?
  posts Post[]
}

model Post {
  id        Int      @id @default(autoincrement())
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
  title     String
  content   String?
  published Boolean  @default(false)
  viewCount Int      @default(0)
  author    User?    @relation(fields: [authorId], references: [id])
  authorId  Int?
  rating    Float
}
```

will generate classes as follows:

`User`:

```ts
import { IsInt, IsDefined, IsString, IsOptional } from 'class-validator';
import { Post } from './';

export class User {
  @IsDefined()
  @IsInt()
  id!: number;

  @IsDefined()
  @IsString()
  email!: string;

  @IsOptional()
  @IsString()
  name?: string | null;

  @IsDefined()
  posts!: Post[];
}
```

## Additional Options

| Option   |  Description                              | Type     |  Default      |
| -------- | ----------------------------------------- | -------- | ------------- |
| `output` | Output directory for the generated models | `string` | `./generated` |

Use additional options in the `schema.prisma`

```prisma
generator class_validator {
  provider   = "prisma-generator-class-validator"
  output     = "./generated-models"
}
```

## Development

This is a Prisma generator that creates TypeScript class models with class-validator decorators based on your Prisma schema.

1. Clone the repository
2. Install dependencies: `npm install`
3. Build the project: `npm run build`
4. Test the generator: `npm test`

## Running Tests

The project includes tests for the helper functions:

```bash
# Run helper function tests (most reliable)
npm test

# Run all tests (including integration tests - may require a valid Prisma schema) 
npm run test:all

# Run tests with watch mode during development
npm run test:watch

# Run tests with coverage report
npm run test:coverage

# Build and run tests
npm run build:test
```

### Testing Notes

Integration tests require a valid Prisma schema and can be more fragile. They're best run in a controlled environment where all dependencies are properly set up.

For regular development, stick to the helper tests (`npm test`) which are faster and more reliable.
npm package: @serviceware/changegen
Description: A changelog manager to avoid merge conflicts.
Author: serviceware
Latest version: 1.0.0

# changegen

CHANGELOG merger.

### Usage

Create a template.md file where the logs are going to be. Check the example project in the source.

`npx changegen init` or `yarn calogen init`

`npx changegen a` to add a new log.
`npx changegen g` to generate the changelog.
`npx changegen p -v 1.2.3` to publish a new version and generate the changelog.
npm package: @servie/events
Description: Tiny type-safe event emitter
Author: Blake Embrey
Latest version: 3.0.0

# Events

[![NPM version][npm-image]][npm-url]
[![NPM downloads][downloads-image]][downloads-url]
[![Build status][build-image]][build-url]
[![Build coverage][coverage-image]][coverage-url]
[![Bundle size][bundlephobia-image]][bundlephobia-url]

> Tiny type-safe event emitter.

## Installation

```
npm install @servie/events --save
```

## Usage

```ts
import { Emitter, once, ALL_EVENTS } from "@servie/events";

// Define an events interface using keys & argument tuples.
interface Events {
  test: [boolean];
  other: [string];
}

// Initialize an `Emitter` using your `Events` interface.
const events = new Emitter<Events>();

// Add or remove listeners.
const listener = (...args) => console.log(args);
const off = events.on("test", listener);

// Emit an event.
events.emit("test", true);

// Listen to _all_ events, i.e. for debugging.
const eachListener = ({ type, args }) => console.log(type, args);
const off = events.on(ALL_EVENTS, eachListener);

// "Once" utility.
const runOnce = (...args) => console.log(args);
once(events, "test", runOnce);

// Remove the listener.
off();
```

## TypeScript

This project is written using [TypeScript](https://github.com/Microsoft/TypeScript) and publishes the definitions directly to NPM.

## License

MIT

[npm-image]: https://img.shields.io/npm/v/@servie/events
[npm-url]: https://npmjs.org/package/@servie/events
[downloads-image]: https://img.shields.io/npm/dm/@servie/events
[downloads-url]: https://npmjs.org/package/@servie/events
[build-image]: https://img.shields.io/github/workflow/status/serviejs/events/CI/main
[build-url]: https://github.com/serviejs/events/actions/workflows/ci.yml?query=branch%3Amain
[coverage-image]: https://img.shields.io/codecov/c/gh/serviejs/events
[coverage-url]: https://codecov.io/gh/serviejs/events
[bundlephobia-image]: https://img.shields.io/bundlephobia/minzip/@servie/events.svg
[bundlephobia-url]: https://bundlephobia.com/result?p=@servie/events
npm package: @serviomi/expo-settings
Description: test-expo-settings
Author: serviom
Latest version: 0.1.0

# expo-settings

My new module

# API documentation

- [Documentation for the latest stable release](https://docs.expo.dev/versions/latest/sdk/settings/)
- [Documentation for the main branch](https://docs.expo.dev/versions/unversioned/sdk/settings/)

# Installation in managed Expo projects

For [managed](https://docs.expo.dev/archive/managed-vs-bare/) Expo projects, please follow the installation instructions in the [API documentation for the latest stable release](#api-documentation). If you follow the link and there is no documentation available then this library is not yet usable within managed projects &mdash; it is likely to be included in an upcoming Expo SDK release.

# Installation in bare React Native projects

For bare React Native projects, you must ensure that you have [installed and configured the `expo` package](https://docs.expo.dev/bare/installing-expo-modules/) before continuing.

### Add the package to your npm dependencies

```
npm install expo-settings
```

### Configure for Android




### Configure for iOS

Run `npx pod-install` after installing the npm package.

# Contributing

Contributions are very welcome! Please refer to guidelines described in the [contributing guide]( https://github.com/expo/expo#contributing).
npm package: @servirglobal/spatial-ui-elements
Description: Spatial UI Element
Latest version: 1.0.0



# Spatial UI Elements

[![Vue.js](https://img.shields.io/badge/vuejs-%2335495e.svg?style=for-the-badge&logo=vuedotjs&logoColor=%234FC08D)](https://vuejs.org/)
[![Nuxtjs](https://img.shields.io/badge/Nuxt-002E3B?style=for-the-badge&logo=nuxtdotjs&logoColor=#00DC82)](https://nuxt.com/)
[![Vuetify](https://img.shields.io/badge/Vuetify-1867C0?style=for-the-badge&logo=vuetify&logoColor=AEDDFF)](https://vuetifyjs.com/)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg?style=for-the-badge)](https://opensource.org/licenses/MIT)
[![SERVIR: Global](https://img.shields.io/badge/SERVIR-Global-green?style=for-the-badge)](https://servirglobal.net)


A UI component library for spatial data visualisation.


## Setup

* Requirement

  * Node : `v22.5.1`
  * NPM: `10.8.2`

* Clone this repository
* Change directory to `spatial-uielements`
* Install the dependencies
```bash
npm install
```

## Contribution

  <summary>Local development</summary>
  
  ```bash
  # Generate type stubs
  npm run dev:prepare
  
  # Develop with the playground
  npm run dev
  
  # Build the playground
  npm run dev:build
  
  # Run ESLint
  npm run lint

  # Run lint fix and prettier format
  npm run fix:format
  ```

  ## Useful Links

  * [Vue](https://vuejs.org/)
  * [Nuxt3](https://nuxt.com/)
  * [Vuetify](https://vuetifyjs.com/)
  * [Leaflet](https://leaflet.nuxtjs.org/)


## Contact

### Software Developers

- [Deepak Shah (NASA/USRA)](https://github.com/deepak-shah-np)
- [Billy Ashmall (NASA/USRA)](https://github.com/billyz313)



## License and Distribution

Spatial UI Elements is distributed by SERVIR under the terms of the {type of license you choose} License. See
[LICENSE](LICENSE) in this directory for more information.

## Privacy & Terms of Use

Spatial UI Elements abides to all of SERVIR's privacy and terms of use as described
at [https://servirglobal.net/Privacy-Terms-of-Use](https://servirglobal.net/Privacy-Terms-of-Use).
npm package: @servis-ai/react-native-webrtc
Description: Servis.ai fork of WebRTC for React Native
Latest version: 118.0.3-servis-ai.1

# @servis-ai/react-native-webrtc

**:warning: This is the Servis.ai fork of `react-native-webrtc`, meant only for use with [`react-native-daily-js`, whose documentation you should refer to for usage information](https://github.com/daily-co/react-native-daily-js). If you're looking for [the standard `react-native-webrtc` useful for a variety of projects, here it is](https://www.npmjs.com/package/react-native-webrtc).**
npm package: @servoy/ngdesktopfile
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 11.2.9.
Latest version: 3.0.2

# Ngdesktopfile

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 11.2.9.

## Code scaffolding

Run `ng generate component component-name --project ngdesktopfile` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project ngdesktopfile`.
> Note: Don't forget to add `--project ngdesktopfile` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build ngdesktopfile` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build ngdesktopfile`, go to the dist folder `cd dist/ngdesktopfile` and run `npm publish`.

## Running unit tests

Run `ng test ngdesktopfile` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @servoy/ngdesktopui
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 11.2.9.
Latest version: 2.0.0

# Ngdesktopui

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 11.2.9.

## Code scaffolding

Run `ng generate component component-name --project ngdesktopui` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project ngdesktopui`.
> Note: Don't forget to add `--project ngdesktopui` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build ngdesktopui` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build ngdesktopui`, go to the dist folder `cd dist/ngdesktopui` and run `npm publish`.

## Running unit tests

Run `ng test ngdesktopui` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @servoy/public
Description: This libray must be used to create component or service packages for the Servoy NGClient Angular based application.
Latest version: 2026.3.0

# Servoy NGClient Public Library

This libray must be used to create component or service packages for the Servoy NGClient Angular based application.

Install it with npm install @servoy/public

The common base for all NGClient components is the ServoyBaseComponent which all components should be extending.

From that components have access through the ServoyApi to the system.  

Components can use the Servoy public directives like svyFormat, svyTooltip, sabloTabseq to map the Servoy spec properties of the component on.
also a few pipes are in this library like TrustAsHtml or FormatFilter

There are also a number of Injectables/Services like a LoggerFactory for add logging support to your component or service. 
A FormattingService if you want to format or unformat data through code 

For a lot of serverside communication there is the ServoyPublicService that can be used by Components or Services to get data, call the service or generate stuff for the server.
Or get a lot of locale specific information like the locale or the decimal character for the clients locale.
npm package: @servoy/tempus-dominus
Description: A robust and powerful date/time picker component. For usage, installation and demos see Project Site on GitHub
Author: Jonathan Peterson
Latest version: 6.0.0-beta5.1

[![ko-fi](https://ko-fi.com/img/githubbutton_sm.svg)](https://ko-fi.com/R6R53OEFF)

[![Rate on Openbase](https://badges.openbase.com/js/rating/@eonasdan/tempus-dominus.svg)](https://openbase.com/js/@eonasdan/tempus-dominus?utm_source=embedded&utm_medium=badge&utm_campaign=rate-badge)

# Tempus Dominus Date/Time Picker v6.0.0-beta5.1

Tempus Dominus is a powerful and robust date time picker for javascript. Version 6 is another major rewrite over the previous version. V6 is written with modern browsers in mind and is written in typescript. Bootstrap, momentjs and jQuery are no longer required dependencies. Popper2 is all that is required for the picker to position correctly. If you still require jQuery (seriously, you should move off that asap) there's a jQuery provider that wraps the native js functions.

# Ready State
The beta is here. There's still plenty of things that can be worked on and you can see the [rough roadmap here](https://github.com/Eonasdan/tempus-dominus/projects). 

# Community

Need help or want to discuss some? Join [the discord](https://discord.gg/BHS9jw9YPf).

Please also take a look at the [discussions](https://github.com/Eonasdan/tempus-dominus/discussions). There are several RFCs (Request For Comment) open and you can help shape the future of the picker by participating in these discussions.

# Developers

## Building

Run `npm i` to install needed packages. 

The docs folder contains the generated documentation site, don't modify this directly as it will be overwritten on build. The dist folder contains the built js/css files.

## Running

You can run `npm run serve` which will start a browser-sync server. Navigate to `http://localhost:3001/` to view the docs.

## Watching for changes
Do not run `npm run serve` at the same time.

Run `npm start`. This runs browser-sync, the build and watchers for the docs, styles, and typescript.

## Where do you use this?
I'd love to know if your public site is using this plugin and list your logo on the documentation site. Leave [create a discussion](https://github.com/Eonasdan/tempus-dominus/discussions/categories/show-your-love) and let me know.

## Priority support is available at an hourly rate.

If you have an urgent request, bug or need installation help, please contact in the discord server.
npm package: @servoy/uppy
Description: Angular component wrappers around Uppy's official UI plugins.
Latest version: 0.2.6

# Uppy Angular Integration

## Build

Run `ng build @uppy/angular` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build @uppy/angular`, go to the dist folder `cd dist/@uppy/angular` and run `npm publish`.

## Running unit tests

Run `ng test @uppy/angular` to execute the unit tests via [Karma](https://karma-runner.github.io).