open-index/open-npm huggingface dataset:
npm package: @gepardec-simon-bauer/ngx-liwest-project-init
Description: A blank schematics
Latest version: 15.0.0-beta.1

# Getting Started With Schematics

This repository is a basic Schematic implementation that serves as a starting point to create and publish Schematics to NPM.

### Testing

To test locally, install `@angular-devkit/schematics-cli` globally and use the `schematics` command line tool. That tool acts the same as the `generate` command of the Angular CLI, but also has a debug mode.

Check the documentation with

```bash
schematics --help
```

### Unit Testing

`npm run test` will run the unit tests, using Jasmine as a runner and test framework.

### Publishing

To publish, simply do:

```bash
npm run build
npm publish
```

That's it!
npm package: @geppettoengine/geppetto-client
Description: Geppetto web frontend. Geppetto is an open-source platform to build web-based tools to visualize and simulate neuroscience data and models.
Latest version: 1.0.0

[![Build Status](https://travis-ci.org/openworm/org.geppetto.frontend.png?branch=master)](https://travis-ci.org/openworm/org.geppetto.frontend)

<p align="center">
  <img src="https://github.com/tarelli/bucket/blob/master/geppetto%20logo.png?raw=true" alt="Geppetto logo"/>
</p>

# Geppetto Client

This is the client library of Geppetto which includes all the frontend components and widgets, the WebSocket API implementation to talk to the backend and all the infrastructure to manage the Geppetto Model in Javascript.

For information about how this fits into [Geppetto](http://www.geppetto.org/) refer to the umbrella project [org.geppetto](https://github.com/openworm/org.geppetto) on GitHub.
npm package: @geprog/eslint-config
Description: ESLint config for Typescript, Vue.js and Jest
Latest version: 2.1.1

# GeProg eslint config

Opinionated eslint config for projects using Vue.js with Typescript and Jest

## Usage

```js
require('@geprog/eslint-config/patch/modern-module-resolution');

module.exports = {
  extends: ['@geprog'],
  parserOptions: {
    project: ['./tsconfig.json'], // should "include" all files you want to lint
    tsconfigRootDir: __dirname,
  },
};
```

## Available configs

- `@geprog`
- `@geprog/eslint-config/vue`
- `@geprog/eslint-config/jest`

## Development

Install dependencies: `pnpm install`
npm package: @geprog/oauth-mock-server
Description: A mocked oauth server for development and e2e testing
Latest version: 1.6.0

# oauth-mock-server

> :rotating_light: IMPORTANT: This tool should ONLY be used for development and testing setups!

A mocked oauth server for development and e2e testing.

## Config

You can adjust the default configuration by placing a file `oauth-mock-server.json` in your current working directory:

```json
{
  "port": 5000,
  "realm": "my-project",
  "users": [
    {
      "id": "1",
      "username": "toni",
      "email": "toni@test.com",
      "name": "Toni Tester"
    },
    {
      "id": "2",
      "username": "alice",
      "email": "alice@wonderland.org",
      "name": "Alice Wonderland"
    },
    {
      "id": "3",
      "username": "herbert",
      "email": "her@bert.de",
      "name": "Herbert"
    }
  ],
  "tokenExpiresIn": 86400 // 24 hours in seconds
}
```
npm package: @geprog/semantic-release-config
Description: semantic-release shareable config to publish NPM packages at Geprog
Author: Geprog GmbH
Latest version: 2.0.0

# @geprog/semantic-release-config

[**semantic-release**](https://github.com/semantic-release/semantic-release) shareable config to publish NPM packages at [Geprog](https://geprog.com/).

[![Build Status](https://github.com/geprog/semantic-release-config/workflows/Test/badge.svg)](https://github.com/geprog/semantic-release-config/actions?query=workflow%3ATest+branch%3Amain) [![npm latest version](https://img.shields.io/npm/v/@geprog/semantic-release-config/latest.svg)](https://www.npmjs.com/package/@geprog/semantic-release-config)
[![npm next version](https://img.shields.io/npm/v/@geprog/semantic-release-config/next.svg)](https://www.npmjs.com/package/@geprog/semantic-release-config)

## Install

```bash
$ npm install --save-dev semantic-release @geprog/semantic-release-config
```

## Usage

The shareable config can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):

```json
{
  "extends": "@geprog/semantic-release-config"
}
```
npm package: @geprog/translator
Description: A simple cli for translations
Latest version: 1.2.0

# Translator

Translator by [Geprog](https://geprog.com) is a simple cli tool to translate `.json` translations files.

## Usage

```bash
# npm
npx  @geprog/translator translate ./my-project/src/locales

# pnpm
pnpx @geprog/translator translate ./my-project/src/locales
```
npm package: @geprog/use-feathers
Description: Vue.js compositions for Feathers
Latest version: 3.3.5

# Vue.js compositions for Feathers

Provides `get` and `find` compositions that let you query your feathers API.  
Queries and responses are fully reactive allowing you to:

- trigger a query by simply updating a query parameter
- receive continuous updates via [@feathersjs/socketio-client](https://docs.feathersjs.com/api/client/socketio.html) that are instantly visible inside Vue components.

## Example usage

Define a wrapper that passes your feathers app.  
Passing your `Application` type including your `ServiceTypes` allows typechecking of the `serviceName` parameter.

```ts
// useFindWrapper.ts
import { useFind } from '@geprog/use-feathers';
import { Application as FeathersApplication } from '@feathersjs/feathers';
import { AdapterService } from '@feathersjs/adapter-commons';
import { Car } from './model';

type ServiceTypes = {
  cars: AdapterService<Car>;
};

type Application = FeathersApplication<ServiceTypes>;

export const useFindWrapper = useFind<Application>(yourFeathersApp);
```

Inside a Vue component call the wrapper with a `serviceName` and a Params ref containing your query.

```ts
import { computed, defineComponent } from 'vue';
import { useFindWrapper } from './useFindWrapper';

export default defineComponent({
  setup() {
    const seats = ref(4);
    const { data: cars, isLoading } = useFindWrapper(
      'cars',
      computed(() => ({ paginate: false, query: { seats: seats.value } })),
    );
    return { seats, cars, isLoading };
  },
});
```
npm package: @geprog/vite-plugin-env-config
Description: Vite Plugin for providing config from environment variables at runtime
Latest version: 4.0.14

# @geprog/vite-plugin-env-config

[![npm version](https://img.shields.io/npm/v/@geprog/vite-plugin-env-config)](https://www.npmjs.com/package/@geprog/vite-plugin-env-config)
![vite peer dependency version](https://img.shields.io/npm/dependency-version/@geprog/vite-plugin-env-config/peer/vite)

Vite plugin for providing configurations from environment variables at runtime.

The generated template can be populated with [envsubst](https://github.com/a8m/envsubst) in production.

## Usage

Add `envConfig` plugin to `vite.config.js / vite.config.ts` and provide a list of environment variable names:

```js
// vite.config.js / vite.config.ts
import { envConfig } from '@geprog/vite-plugin-env-config';

export default {
  plugins: [envConfig({ variables: ['BACKEND_URL'] })],
};
```

To access the environment variables use the built-in getter:

```ts
import { getEnvConfig } from '@geprog/vite-plugin-env-config';

const backendURL = getEnvConfig('BACKEND_URL');
```

For production use `envsubst` as outlined in the [next section](#motivation).

## Motivation

To adhere to the principles of the [twelve-factor app](https://12factor.net/config)
you might need to access environment variables that are set when your frontend server starts.
Instead of building your frontend on startup,
you can use a config template like the one above and populate it using `envsubst`:

```Dockerfile
CMD ["/bin/sh", "-c", "envsubst < ./dist/env-config.template.js > ./dist/env-config.js && exec nginx -g 'daemon off;'"]
```

`@geprog/vite-plugin-env-config` generates the required template from a list of variable names and provides the already populated file via the dev-server during development.
npm package: @geprom/eslint-prettier-sapient
Description: ESLint and Prettier configuration for Geprom Sapient projects with snake_case and camelCase support
Author: GEPROM
Latest version: 1.0.5

# @geprom/eslint-prettier-sapient

ESLint and Prettier configuration for Geprom Sapient projects with support for both camelCase and snake_case naming conventions.

## Installation

```bash
npm i @geprom/eslint-prettier-sapient
```

## Features

- ✅ Airbnb ESLint ruleset
- ✅ Prettier integration
- ✅ Both camelCase and snake_case naming support
- ✅ Preconfigured globals: `DbCon`, `DbQuery`, `logger`

## Configuration Details

### Supported Naming Conventions

Both naming styles are accepted without warnings:

- `someFunction` (camelCase)
- `some_function` (snake_case)

### Application Globals

These globals are pre-declared and don't require imports, any additional global variable available in Sapient should :

- `DbCon` - Database connection class
- `DbQuery` - Database query class
- `logger` - Logger instance

To extend with additional globals:

```javascript
module.exports = {
  extends: ['@geprom/eslint-prettier-sapient'],
  globals: {
    myCustomGlobal: 'readonly',
  },
};
```

### ESLint Rules

- **camelcase**: Flexible naming - accepts both camelCase and snake_case patterns
- **jsx-a11y/href-no-hash**: Disabled
- **react/jsx-filename-extension**: Warns for .js files (allows .jsx)
- **max-len**: 100 character limit with exceptions for comments, URLs, and strings
- **react/prop-types**: Warning level
- **no-unused-vars**: Ignores variables starting with underscore

### Prettier Options

- **printWidth**: 100 characters
- **singleQuote**: true
- **trailingComma**: 'es5'
- **bracketSpacing**: true
- **semi**: true
- **useTabs**: false
- **tabWidth**: 2 spaces
- **arrowParens**: 'always'

## Extending the Configuration

You can extend or override rules in your project's `.eslintrc.js`:

```javascript
module.exports = {
  extends: ['@geprom/eslint-prettier-sapient'],
  rules: {
    'max-len': ['warn', { code: 120 }], // Override max line length
    'no-console': 'warn', // Add custom rule
  },
};
```
npm package: @geps/geofs-types
Description: Types for the GeoFS API.
Latest version: 1.0.1

# GeoFS Types

GeoFS' API is pretty mysterious, since its true source code has never popped into the public's view. This repo, and its associated npm package, aims to demystify it.

## How to use

You need to install the package from npm.

```sh
npm install @geps/geofs-types
```

Since this isn't an `@types` package, the TypeScript compiler won't automatically pick up these types. Because of that, you will need to manually request that the TypeScript compiler use these types.

The preferred method to use these types is through a [triple-slash directive](https://www.typescriptlang.org/docs/handbook/triple-slash-directives.html), like so:

```ts
/// <reference types="jquery" />
/// <reference types="@geps/geofs-types" />
```

You will then be able to access the types. Be careful to also include the JQuery types, as the types rely on them.

If the previous method doesn't work for your use case, you will have to manually specify these types in the `tsconfig.json` of your project. It will look something like this:

```json
{
  "compilerOptions": {
    "types": ["@geps/geofs-types", "jquery"]
  }
}
```

**WARNING**: Be aware that when you declare the `types` property in your tsconfig, it turns off the compiler's ability to pick up types. You will have to add types to the tsconfig.

**WARNING**: These types rely on JQuery's types, so when you declare these types in your tsconfig, you must be careful to also declare JQuery's types in the tsconfig.

<!-- ## How to contribute

We accept PRs! Read our [contributing guide](./CONTRIBUTING.md) for more info. -->