open-index/open-npm huggingface dataset:
npm package: @nuagedelait/react-scrollspy
Description: react scroll handler component
Author: Oliver White
Latest version: 1.0.0

# react-scrollspy

React scrollspy component

This component is under development

#### Roadmap :
Export dist

## install
```
npm install @nuagedelait/react-scrollspy --save
```

## use

You should compose the element you want to spy with the ScrollSpy. It renders and Fragment so it will not mess with your dom structure.
If you compose several items, the first one will be the reference and will receive classes and data

#### Roadmap :
add data and classes to all child elements.

```
import ScrollSpy from '@nuagedelait/react-scrollspy';

const Component = (props) => {

  return(
    <ScrollSpy>

    ... Content to animate

    </scrollspy>

  )
}

```

## result

The component add class ```inview``` to his reference if the element top/left corner enter the view.

The reference receive also a progress status from -1 to 1 (right to left or bottom to top) and associated classes :

|bottom|center|top|
|-|-|-|
|inviewY_b_100, inviewY_b_90, inviewY_b_80,...,inviewY_b_10 |inviewY_0|inviewY_t_10,inviewY_t_20,...,inviewY_t_100|

|right|center|left|
|-|-|-|
|inviewX_r_100, inviewY_r_90, inviewX_r_80,...,inviewX_r_10 |inviewX_0|inviewX_l_10,inviewX_l_20,...,inviewX_l_100|

#### Roadmap :
Handle only top/left corner or full object.

```
<img class="inview inviewY_b_20" delta={deltaX:0,deltaY:0.2}/>
```


## Options

```
ex : <ScrollSpy offsetX={100} delayIn={200}/>
```

|option|type|unit|effect|default|
|-|-|-|-|-|
|offsetX|number|px|horizontal offset on trigger in /  out (left and right)|0|
|offsetY|number|px|vertical offset on trigger in / out (left and right)|100|
|delayIn|number|ms|delay on trigger in view|0|
|delayOut|number|ms|delay on trigger out view|0|
|animateOnce|boolean|true/false|once in is trigger, never trigger in or out anymore|false|
|ignoreX|boolean|true/false|ignore horizontal scroll|true|
|ignoreY|boolean|true/false|ignore vertical scroll|false|
|target|mixed|"parent" or dom element|set another dom lement or the parent of the spy as reference|null (use the first child))|
npm package: @nuanc/core
Description: A notion utility package focused on tracking changes, it also comes with a CLI!
Author: Henrique Cunha
Latest version: 1.2.1

# Nuanc
A notion utility package focused on tracking changes, it also comes with a CLI!

## Installation
Clone this repository and run
```bash
yarn
npm link
```

## Usage
```bash
export NOTION_TOKEN={token}
nuance -h
```
npm package: @nuanced-dev/jellycg
Description: Jelly - call graph and library usage analyzer for JavaScript
Author: Anders Møller
Latest version: 0.10.1

# Jelly (Nuanced)

## Release Process

1. Run the release script:

   ```sh
   script/release
   ```

   This does some basic checks, creates a new version tag from the `package.json` version, and pushes that to GitHub.
   That triggers the workflow that creates the actual release.

2. Publish the release via Anystack UI.
npm package: @nuanced-dev/lsp-morphcloud
Description: CLI to run Nuanced LSP on Morphcloud
Author: Nuanced
Latest version: 0.1.2

# Nuanced LSP Morph Cloud Client

This is a client to run Nuanced LSP remotely on [Morph Cloud](https://cloud.morph.so).

_Note that this client is experimental and not considered stable!_

**Current features:**

- Run Nuanced LSP instances for a workspace remotely in the Morph Cloud.
- Sync files from the local workspace to the remote instance.
- Resume a previous LSP instance for the same workspace for fast startup.

**Known issues:**

- Mutagen easily gets into error states, where resuming syncs hangs or setting up syncs fails. Often the only way to recover is removing the mutagen data directory (`~/.nuanced/mutagen`).
- File syncs are sometimes not properly resumed, in which case the workspace instance needs to be recreated.
- Morph Cloud retains snapshots for instances that have been deleted. These snapshots do not inherit the metadata of the instance and we currently cannot clean them up.

**Future possibilities:**

- Use instances from other branches of the same repo to improve cold start time. For example, if an instance is available for the main branch, feature branches could start from that and reuse existing state as much as possible.
- Support creating multiple, named, service snapshots with different resource or languages preloaded.

## Requirements

- Recent Node.js version installed
- A [Morph Cloud](https://cloud.morph.so) account, and an API token in the `MORPH_API_KEY` environment variable.

## Quick start

**Create the service snapshot:**

```bash
nuanced-lsp-morphcloud service create
```

This creates the base snapshot from which the workspace instances are spawned.

**Check service status:**

```bash
nuanced-lsp-morphcloud service status
```

**Delete service snapshot:**

```bash
nuanced-lsp-morphcloud service delete
```

This can be useful if you want to recreate the service snapshot. The old snapshot must be removed first.

**Start a remove LSP server for a workspace:**

```bash
nuanced-lsp-morphcloud workspace server /path/to/workspace
```

**Check workspace status:**

```bash
nuanced-lsp-morphcloud workspace status /path/to/workspace
```

**Remove a workspace status:**

```bash
nuanced-lsp-morphcloud workspace delete /path/to/workspace
```

This can be useful if you want to recreate the workspace instance.

**List workspaces:**

```bash
nuanced-lsp-morphcloud workspace list
```

## Troubleshooting

**Mutagen sync setup fails:**

Starting a workspace server fails with an error like the following:

```
Connecting to agent (POSIX)...
Error: unable to connect to beta: unable to connect to endpoint: unable to dial agent endpoint: unable to handshake with agent process: unable to receive server magic number: EOF (error output: No user exists for uid 504)
```

Mutagen got in a bad state. Remove `~/.nuanced/mutagen` to have syncs recreated.

## License

This work is licensed under the terms of the MIT license. For a copy, see [LICENSE](LICENSE) or <https://opensource.org/licenses/MIT>.
npm package: @nuarch/covalent.core
Description: Teradata UI Platform built on Angular Material
Author: Teradata UX
Latest version: 2.0.0-nuarch.20

# core

Core Teradata UI Platform for layouts, icons, custom components and themes. This should be added as a dependency for any project that wants to use layouts, icons and themes for Angular Material.

The core will have custom components that enforce standards and best practices through built-in design patterns.


## Installation

This component can be installed as npm package.

```bash
npm i -save @covalent/core
```


## Setup

Import the modules from `@covalent/core` as needed in your NgModule:

```typescript
import { CovalentLayoutModule } from '@covalent/core/layout';
import { CovalentStepsModule  } from '@covalent/core/steps';
/* and many more */
@NgModule({
  imports: [
    CovalentLayoutModule,
    CovalentStepsModule,
    ...
  ],
  ...
})
export class MyModule {}
```


## Styles, Icons and Theming

See [theming](https://teradata.github.io/covalent/#/docs/theme) in the covalent docs for more info

Core Teradata UI Platform comes with a base CSS file `@covalent/core/common/platform.css` (includes icons).
npm package: @nuarch/covalentcore
Description: Teradata UI Platform built on Angular Material
Author: Teradata UX
Latest version: 2.0.1-nuarch.42

# core

Core Teradata UI Platform for layouts, icons, custom components and themes. This should be added as a dependency for any project that wants to use layouts, icons and themes for Angular Material.

The core will have custom components that enforce standards and best practices through built-in design patterns.


## Installation

This component can be installed as npm package.

```bash
npm i -save @covalent/core
```


## Setup

Import the modules from `@covalent/core` as needed in your NgModule:

```typescript
import { CovalentLayoutModule } from '@covalent/core/layout';
import { CovalentStepsModule  } from '@covalent/core/steps';
/* and many more */
@NgModule({
  imports: [
    CovalentLayoutModule,
    CovalentStepsModule,
    ...
  ],
  ...
})
export class MyModule {}
```


## Styles, Icons and Theming

See [theming](https://teradata.github.io/covalent/#/docs/theme) in the covalent docs for more info

Core Teradata UI Platform comes with a base CSS file `@covalent/core/common/platform.css` (includes icons).