open-index/open-npm huggingface dataset:
npm package: @seismicdev/serene-angular
Description: Angular proxies for @seismicdev/serene
Latest version: 0.0.2

# Angular

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

## Development server

Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The application will automatically reload if you change any of the source files.

## Code scaffolding

Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.

## Build

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

## Running unit tests

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

## Running end-to-end tests

Run `ng e2e` to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.

## 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: @seismo/core
Description: This is the package for the core library of Seismo, a JavaScript library for seismic data processing and visualization. It provides utilities for handling seismic data, including FDSN web services, waveform processing, and event handling. The library is d
Author: Yaman Ozakin https://gulyamani.com
Latest version: 0.0.4

# What Is This?

This is a refactoring of [seisplotjs](https://github.com/crotwell/seisplotjs) codebase by Philip Crotwell, by splitting it into server and client side workspaces. 

The aim is to make it possible to run it in a non-browser environment and make contribution easier as pointed out by [baagaard-usgs](https://github.com/crotwell/seisplotjs/issues/1).
npm package: @seismo/web
Description: This is a refactoring of [seisplotjs](https://github.com/crotwell/seisplotjs) codebase by Philip Crotwell, by splitting it into server and client side workspaces.
Author: Yaman Ozakin https://gulyamani.com
Latest version: 0.0.2

# What Is This?

This is a refactoring of [seisplotjs](https://github.com/crotwell/seisplotjs) codebase by Philip Crotwell, by splitting it into server and client side workspaces. 

The aim is to make it possible to run it in a non-browser environment and make contribution easier as pointed out by [baagaard-usgs](https://github.com/crotwell/seisplotjs/issues/1).
npm package: @seitau/vibechecker
Description: Local code review made simple - review diffs with inline comments
Author: seitau
Latest version: 0.3.0

# ✅ vibechecker

Local code review made simple - review diffs with inline comments.

## Features

- 📝 **Interactive Diff Review**: Visual diff viewer with syntax highlighting
- 💬 **Inline Comments**: Add comments directly on specific lines
- 🌳 **File Tree View**: Navigate changes in a hierarchical folder structure
- 📋 **Export to Markdown**: Copy all comments with context to clipboard
- 📦 **Export to JSON**: Save review data for later
- 🔄 **Git Integration**: Auto-load diffs from current branch
- 🌲 **Worktree Support**: Switch between different git worktrees
- 💾 **Auto-save**: Your review is automatically saved per workspace

## Installation

```bash
npx @seitau/vibechecker
```

Or install globally:

```bash
npm install -g @seitau/vibechecker
vibechecker
```

## Usage

1. **Start vibechecker**:
   ```bash
   npx @seitau/vibechecker
   ```

2. The tool will automatically:
   - Start a local server on port 3001
   - Open your browser at http://localhost:5173
   - Load the diff from your current git branch

3. **Review workflow**:
   - Click on any line in the diff to add a comment
   - Use the file tree on the left to navigate between files
   - Comments are automatically saved to localStorage
   - Export your review using the floating buttons (📋 for Markdown, 📦 for JSON)

## Development

```bash
# Clone the repository
git clone https://github.com/seitau/vibechecker.git
cd vibechecker

# Install dependencies
npm install

# Start development servers
npm run dev
```

## Project Structure

```
vibechecker/
├── frontend/       # React + Vite frontend
├── server/         # Express API server
├── shared/         # Shared TypeScript types
└── bin/            # CLI executable
```

## License

MIT
npm package: @seithq/ncalayer
Description: A small wrapper around NCALayer websocket API.
Author: Daniyar Baitursynov
Latest version: 1.1.1

# NCALayerJS

A small wrapper around [NCALayer](https://pki.gov.kz/en/ncalayer-2/) websocket API.

## Installation

```sh
npm install @seithq/ncalayer
```

or

```sh
yarn add @seithq/ncalayer
```

## Usage

```javascript
import Client from "@seithq/ncalayer"

// Initialize websocket connection with running NCALayer.
let ws = new WebSocket("wss://127.0.0.1:13579/")

// Handle onopen, onerror and onclose events as you want.
ws.onopen = (e) => {
  // your code goes here
}

ws.onerror = (e) => {
  // your code goes here
}

ws.onclose = (e) => {
  // your code goes here
}

// Initialize client to work with API.
const client = new Client(ws)

// Call API method.
client.browseKeyStore("PKCS12", "P12", "", (data) => {
  // on success
  if (data.isOk()) {
    // some action
  }

  // on failure
  console.error(data)
})
```

## Demos

- [React](https://github.com/seithq/ncalayer-react)
- [Stimulus](https://github.com/seithq/ncalayer-stimulus)

## Maintainers

[@danikarik](https://github.com/danikarik)

## License

This project is licensed under the [MIT License](LICENSE).
npm package: @seivad/sync
Description: Sync all of our packages with Composer, Git, NPM, etc...
Author: Mick Davies
Latest version: 1.0.2

# Sync Package

This package simplifies updating and syncing projects within your directories. 

Simply provide a list of the directories you want to be automatically synchronized. 

Currently supports the following:

- **NPM**
- **Composer**
- **Laravel / Artisan**


## Clone the package locally

Pull in the package locally to make adjustments / edits:

```
git@gitlab.com:universaltechnology/SnapTrack/packages/sync.git
```

You can provide a custom projects.json file by saving this file in your user directory and running the following flag:

```
sync -p Sites/projects.json
```

**Example projects.json File**

```
[
	{
		"folder": "Sites/snaptrack/assets",
		"steps": ["npm", "composer", "artisan"]
	},
	{
		"folder": "Sites/snaptrack/auth",
		"steps": ["npm", "composer", "artisan"]
	}
]
```

## Update Projects To Sync

To update the projects.json file after installing locally, navigate to the following folder directory to edit the file:

```
/usr/local/lib/node_modules/sync/projects.json
```

**Note** Do not forget to remove the final trailing comma to make this a valid JSON document, if you leave the final comma after the last object, it will throw an error.

## Updates

To pull in updates of the globally installed package, run the following:

```
npm install -g @seivad/sync
```


## Steps

**Step Options Available**
- composer
- artisan
- npm


## Order

Currently the options will run in the following order

- composer
- artisan
- npm


## Install the sync helper globally

To be able to run the sync helper from any directory, please install globally using the command below:

**From the package**
```
npm install -g .
```

**From NPM Repository**
```
npm install -g @seivad/sync
```


## Run the Sync Helper

Examples include:

Defaults to *local* development environment and *staging* branch
```
node . 
```

or provide the specific development environment and branch you require
```
node . --branch master --env production
```

or if installed globally:

```
sync --projects Sites/projects.json
```

## Composer

The Composer step will run the following command

- composer update


## Artisan

The Artisan (Laravel) step will run the following commands

- php artisan migrate --force --no-interaction
- php artisan config:clear
- php artisan route:clear
- php artisan cache:clear
- php artisan queue:restart


## NPM

The NPM step will run the following commands

- npm install
- npm run {environment; defaults to local}
npm package: @seiyab/eslint-plugin-react-hooks
Description: ESLint rules for React Hooks
Latest version: 4.5.1-beta.0

# `@seiyab/eslint-plugin-react-hooks`

This is alternative to eslint-plugin-react-hooks because of https://github.com/facebook/react/issues/16265

## Installation

Assuming you already have ESLint installed, run:

```sh
# npm
npm install @seiyab/eslint-plugin-react-hooks --save-dev

# yarn
yarn add @seiyab/eslint-plugin-react-hooks --dev
```

Then extend the recommended eslint config:

```js
{
  "extends": [
    // ...
    "plugin:@seiyab/react-hooks/recommended"
  ]
}
```

### Custom Configuration

If you want more fine-grained configuration, you can instead add a snippet like this to your ESLint configuration file:

```js
{
  "plugins": [
    // ...
    "@seiyab/eslint-plugin-react-hooks"
  ],
  "rules": {
    // ...
    "@seiyab/react-hooks/rules-of-hooks": "error",
    "@seiyab/react-hooks/exhaustive-deps": "warn"
  }
}
```


## Advanced Configuration
### additionalHooks
`exhaustive-deps` can be configured to validate dependencies of custom Hooks with the `additionalHooks` option.
This option accepts a regex to match the names of custom Hooks that have dependencies.

```js
{
  "rules": {
    // ...
    "@seiyab/react-hooks/exhaustive-deps": ["warn", {
      "additionalHooks": "(useMyCustomHook|useMyOtherCustomHook)"
    }]
  }
}
```

We suggest to use this option **very sparingly, if at all**. Generally saying, we recommend most custom Hooks to not use the dependencies argument, and instead provide a higher-level API that is more focused around a specific use case.

### ignoreThisDependency
You may find `exhaustive-deps` requires entire `props` if you use something like `props.doSomething()` in hooks.
This is intended behavior because `props` is referred as `this` by `doSomething`.
You can resolve it by destructuring as `exhaustive-deps` suggests.

However, in some cases, you may want to avoid destructuring because of your coding style or conflict with `no-shadow`.
In the case, `ignoreThisDependency` may help.

```js
{
  "rules": {
    // ...
    "@seiyab/react-hooks/exhaustive-deps": ["warn", {
      "ignoreThisDependency": "props"
    }]
  }
}
```

Valid options are `never` (default behavior), `props`, `always`.

## Valid and Invalid Examples

Please refer to the [Rules of Hooks](https://reactjs.org/docs/hooks-rules.html) documentation and the [Hooks FAQ](https://reactjs.org/docs/hooks-faq.html#what-exactly-do-the-lint-rules-enforce) to learn more about this rule.

## License

MIT
npm package: @seiyab/fp-ts-react-query
Description: fp-ts bindings for react-query
Author: seiyab
Latest version: 0.0.2

# fp-ts-react-query
[fp-ts](https://github.com/gcanti/fp-ts) bindings for [React Query](https://github.com/tannerlinsley/react-query/)

Helps following
- Apply function to return of useQuery iff data exists
- Compose multiple query results
- Deal success result as idle / loading / error according to data

## Examples
### apply function iff data exists
```ts
import * as UQR from 'fp-ts-react-query/UseQueryResult';

const f = (x: number): string => `got ${x}`;
const liftedF = UQR.map(f)

const Component: React.FC = () => {
  const raw: UseQueryResult<number> = useQuery('query1', () => someQuery());
  const calculated: UseQueryResult<string> = liftedF(raw);
  // ...
};
```

raw | calculated
:- | :-
success(1) | success('got 1')
success(2) | success('got 2')
idle | idle
loading | loading
error | error

### compose two query results
```ts
import { pipe } from "fp-ts/lib/function";
import * as UQR from 'fp-ts-react-query/UseQueryResult';

const Component: React.FC = () => {
  const x: UseQueryResult<number> = useQuery('query1', () => someQuery1());
  const y: UseQueryResult<number> = useQuery('query2', () => someQuery2());
  const calculated: UseQueryResult<string> = pipe(
    UQR.Do,
    UQR.bind('a', () => x), // bind x as 'a'
    UQR.bind('b', () => y), // bind y as 'b'
    UQR.map({a, b} => a * 5 + b)
  );
  // ...
};
```

x | y | calculated
:- | :- | :-
success | success | success(x.data * 5 + y.data)
idle | success | idle
loading | success | loading
error | success | error
success | idle | idle
... | ... | ...

### compose many query results
```ts
import { pipe } from "fp-ts/lib/function";
import * as UQR from 'fp-ts-react-query/UseQueryResult';

const Component: React.FC = () => {
  const w = useQuery('query1', () => someQuery1());
  const x = useQuery('query2', () => someQuery2());
  const y = useQuery('query3', () => someQuery3());
  const z = useQuery('query4', () => someQuery4());
  const calculated = pipe(
    UQR.Do,
    UQR.bind('a', () => w),
    UQR.bind('b', () => x),
    UQR.bind('c', () => y),
    UQR.bind('d', () => z),
    UQR.map({a, b, c, d} => {
      // ... complex computation
    })
  );
  // ...
};
```

### Deal success result as idle / loading / error according to data
```ts
import * as UQR from 'fp-ts-react-query/UseQueryResult';

const f = (a: number): UseQueryResult<number> => {
  if (a < 0) return UQR.error();
  if (a === 0) return UQR.idle();
  return UQR.success(a * 5)
}

const Component: React.FC = () => {
  const x = useQuery('query1', () => someQuery1());
  const calculated = UQR.chain(f)(x);
  // ...
};
```

x | calculated
:- | :-
success(10) | success(50)
success(0) | idle
success(-3) | error
idle | idle
loading | loading
error | error

## Implemented instances
- `Monad`
npm package: @seiyab/that
Description: that
Author: seiyab
Latest version: 0.1.0-alpha.0

# That
`that` is user-space implementation for `call-this`, inspired by [Call-this operator for JavaScript](https://github.com/tc39/proposal-call-this) proposal.

# Examples
```ts
function increment(this: number): number {
    return this + 1;
}

function add(this: number, another: number): number {
    return this + another;
}

// call-this operator
that(8)
    ['~>'](increment)
    ['~>'](add, 5)
    ['~>'](add, 9)[';'];
// => 23

// Hack pipe
that('Hello, world!')
    ['|>'](($) => $.split(" "))
    ['|>'](($) => $.length)
    ['|>'](($) => Math.pow(3, $))[';'];
// => 9

// Optional chain
that([1, 2, 3, 4])
    ['|>'](($) => $.find((x) => x < 0))
    ['?|>'](($) => $ + 2)[';'];
// => undefined
```

# Installation
`that` is not published yet.
npm package: @seiyria/oath-parser
Description: A parser to reverse-engineer Oath Board Game TTS savefiles.
Author: Kyle Kemp
Latest version: 1.0.8

# OathParser
A parser to reverse-engineer Oath TTS savefiles

## Installation

`npm i oath-parser`

## Usage

```
import { parseOathTTSSavefileString } from '@seiyria/oath-parser'

parseOathTTSSavefileString(yourSavefile);
```

You can see an example of this in `test/savefile.ts`.

## References

The Lua code is kept in `lua/`. It's copy/pasted out of the TTS mod for easier reference. It's not guaranteed to be up to date.

## Future

Serialize a savefile string by passing in a JSON object.

## Credits

- Cole & Leder Games: making this great game (& letting me make cool stuff)
- AgentElron: having such readable code!
npm package: @seiyria/rootlog-parser
Description: A parser to parse Rootlog games.
Author: Kyle Kemp
Latest version: 1.4.0

# RootlogParser
A parser to turn Rootlog games into JSON to be consumed.

## Installation

`npm i @seiyria/rootlog-parser`

## Usage

```
import { parseRootlog } from '@seiyria/rootlog-parser'

parseRootlog(yourRootlog);
```

You can see an example of this in `test/rootlog.ts`.

## Future

Serialize a savefile string by passing in a JSON object.

## Credits

- Cole & Leder Games: making this great game (& letting me make cool stuff)
- Alex: making Rootlog!