open-index/open-npm huggingface dataset:
npm package: @opennem/energy-tools
Description: OpenNEM energy functions in Javascript
Author: Nik Cubrilovic
Latest version: 1.5.1

# OpenNEM Energy Functions

Energy functions in Javascript.

## Install

```sh
$ yarn add @opennem/energy-tools
```

## Functions

```js
/**
 * Calculate energy sum
 *
 * @param series power values
 * @param bucket_size_minutes size of the bucket in minutes
 */
export function energy_sum(
  series: number[],
  bucket_size_minutes: number,
): number
```

## Usage

```js
import { energy_sum } from "@opennem/energy-tools"

let energy = energy_sum([1, 2], 5)
```
npm package: @opennetwork/conventions
Description: ##
Latest version: 2.0.0

# Conventions

## 


## UI

All visual state will be represented as jsx, this allows flexibility around the target runtime

```typescript
export const Hello = <>
  <title>Hello!</title>
  <header>Hello!</header>
</>
```

UI Components can be defined using a function, this allows information to be serialized into a visual representation

```typescript
export interface Article {
   content: unknown
   title: unknown
}

export function DisplayArticle(this: Article) {
  return <>
    <title>{this.title}</title>
    <article>
      <header>{this.title}</header>
      {this.content}
    </article>
  </>
}
```
npm package: @opennetwork/dataset
Description: In memory dataset for both sync and async contexts, based of (but not conforming to) [https://rdf.js.org/dataset-spec/](https://rdf.js.org/dataset-spec/)
Latest version: 6.0.0
Deprecated: In favour of https://github.com/opennetwork/lazy-set

# Dataset

In memory dataset for both sync and async contexts, based of (but not conforming to) [https://rdf.js.org/dataset-spec/](https://rdf.js.org/dataset-spec/)
npm package: @opennetwork/environment
Description: Cross platform JavaScript environment
Author: Fabian Cook
Latest version: 1.23.0

# @opennetwork/environment

Cross platform JavaScript environment

[//]: # (badges)

![nycrc config on GitHub](https://img.shields.io/nycrc/virtualstate/x) ![41.56%25 lines covered](https://img.shields.io/badge/lines-41.56%25-yellow) ![41.56%25 statements covered](https://img.shields.io/badge/statements-41.56%25-yellow) ![53.1%25 functions covered](https://img.shields.io/badge/functions-53.1%25-yellow) ![70.6%25 branches covered](https://img.shields.io/badge/branches-70.6%25-yellow)

[//]: # (badges)

## Usage

```typescript
import {run, addEventListener, fetch} from "@opennetwork/environment"; 
import {Response} from "@opennetwork/http-representation";

addEventListener("install", async () => {
   console.log("Setup something!"); 
});

addEventListener("configure", async () => {
    console.log("Updated configuration for something!");
});

addEventListener("fetch", async (event) => {
    event.respondWith(new Response("Not Found", {
        status: 404
    }))
});

addEventListener("execute", async () => {
    const response = await fetch("/something");
    console.log("Response status: ", response.status);
    console.log("Done something!");
});

await run({
    /* config here */
})
```
npm package: @opennetwork/progressive-merge
Description: Merge a growing list of values that can be loading in parallel with different resolution times
Latest version: 5.5.0

# Progressive Merge

Take a set of async iterations and turn them into an array of the latest values for that iterator. 

This is the general function signature to achieve this:

```typescript
export async function *merge<T>(iterables: AsyncIterable<AsyncIterable<T>>): AsyncIterable<ReadonlyArray<T | undefined>> {
```

This allows us to take multiple functions producing values and group an update set together.

```typescript
import { merge } from "@opennetwork/progressive-merge";

for await (const set of merge([[1, 2, 3, 4], [5, 6, 7, 8, 9]])) {
    console.log(set);
}
```

The above logs:

```
[ 1, 5 ]
[ 2, 6 ]
[ 3, 7 ]
[ 4, 8 ]
[ 4, 9 ]
```
npm package: @opennetwork/rdf-data-model
Description: Implementation of [https://rdf.js.org/data-model-spec/](https://rdf.js.org/data-model-spec/)
Author: Fabian Cook
Latest version: 6.2.0

# RDF Data Model

Implementation of [https://rdf.js.org/data-model-spec/](https://rdf.js.org/data-model-spec/)
npm package: @opennetwork/rdf-dataset
Description: Loose in memory implementation of [https://rdf.js.org/dataset-spec/](https://rdf.js.org/dataset-spec/)
Author: Fabian Cook
Latest version: 13.0.0

# RDF Dataset

Loose in memory implementation of [https://rdf.js.org/dataset-spec/](https://rdf.js.org/dataset-spec/)
npm package: @opennetwork/rdf-dataset-async
Description: Loose in memory implementation of [https://rdf.js.org/dataset-spec/](https://rdf.js.org/dataset-spec/)
Author: Fabian Cook
Latest version: 1.0.3

# RDF Dataset

Loose in memory implementation of [https://rdf.js.org/dataset-spec/](https://rdf.js.org/dataset-spec/)
npm package: @opennetwork/rdf-stream
Description: Loose in memory implementation of [https://rdf.js.org/stream-spec/](https://rdf.js.org/stream-spec/)
Latest version: 1.0.0

# RDF Stream

Loose in memory implementation of [https://rdf.js.org/stream-spec/](https://rdf.js.org/stream-spec/)

Primary differences:

- No internal use of `EventEmitter`, in favour of `AsyncIterable` & `Promise`
- Allows import of `QuadLike` which means we can pass direct JSON objects to it
- Allows import of `Iterable` as well as `AsyncIterable`
- Allows import from `ReadableStream` as it is an `AsyncIterable`
npm package: @opennetwork/vdom-react
Description: ## Contributing
Latest version: 7.0.0

# `vdom-react` - Compat for react with `vnode`

## Contributing

Please see [Contributing](./CONTRIBUTING.md)

## Code of Conduct 

This project and everyone participating in it is governed by the [Code of Conduct listed here](./CODE-OF-CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [conduct@open-network.dev](mailto:conduct@open-network.dev).

## Licence

This repository is licensed under the [MIT](https://choosealicense.com/licenses/mit/) license.
npm package: @opennetwork/vnode
Description: > The exported signature of this project is not expected to change significantly. > This project follows strict [semantic versioning](https://semver.org/), and any change to the exported signature > will result in either a minor version change for additio
Latest version: 27.1.0

# `vnode` - Virtual Node State Manager

> The exported signature of this project is not expected to change significantly.
> This project follows strict [semantic versioning](https://semver.org/), and any change to the exported signature
> will result in either a minor version change for additional signatures, 
> or a major version change for modifications to signatures or removal of a signature

## [Type Documentation](https://iterable.dev/iterable-h)

## Contributing

Please see [Contributing](./CONTRIBUTING.md)

## Code of Conduct 

This project and everyone participating in it is governed by the [Code of Conduct listed here](./CODE-OF-CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [conduct@open-network.dev](mailto:conduct@open-network.dev).

## Licence

This repository is licensed under the [MIT](https://choosealicense.com/licenses/mit/) license.
npm package: @opennetwork/vnode-fragment
Description: > The exported signature of this project is not expected to change significantly. > This project follows strict [semantic versioning](https://semver.org/), and any change to the exported signature > will result in either a minor version change for additio
Latest version: 9.0.0
Deprecated: See @opennetwork/vnode-hooks-extended

# `vnode-fragments` - Fragment helpers for `vnode`

> The exported signature of this project is not expected to change significantly.
> This project follows strict [semantic versioning](https://semver.org/), and any change to the exported signature
> will result in either a minor version change for additional signatures, 
> or a major version change for modifications to signatures or removal of a signature

## Contributing

Please see [Contributing](./CONTRIBUTING.md)

## Code of Conduct 

This project and everyone participating in it is governed by the [Code of Conduct listed here](./CODE-OF-CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [conduct@open-network.dev](mailto:conduct@open-network.dev).

## Licence

This repository is licensed under the [MIT](https://choosealicense.com/licenses/mit/) license.
npm package: @opennetwork/vnode-hooks
Description: > The exported signature of this project is not expected to change significantly. > This project follows strict [semantic versioning](https://semver.org/), and any change to the exported signature > will result in either a minor version change for additio
Latest version: 11.1.0

# `vnode-hooks` - Hooks for `vnode`

> The exported signature of this project is not expected to change significantly.
> This project follows strict [semantic versioning](https://semver.org/), and any change to the exported signature
> will result in either a minor version change for additional signatures, 
> or a major version change for modifications to signatures or removal of a signature

## Contributing

Please see [Contributing](./CONTRIBUTING.md)

## Code of Conduct 

This project and everyone participating in it is governed by the [Code of Conduct listed here](./CODE-OF-CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [conduct@open-network.dev](mailto:conduct@open-network.dev).

## Licence

This repository is licensed under the [MIT](https://choosealicense.com/licenses/mit/) license.
npm package: @opennetwork/vnode-hooks-extended
Description: > The exported signature of this project is not expected to change significantly. > This project follows strict [semantic versioning](https://semver.org/), and any change to the exported signature > will result in either a minor version change for additio
Latest version: 10.0.2

# `vnode-hooks-extended` - Extended hooks for `vnode`

> The exported signature of this project is not expected to change significantly.
> This project follows strict [semantic versioning](https://semver.org/), and any change to the exported signature
> will result in either a minor version change for additional signatures,
> or a major version change for modifications to signatures or removal of a signature

## Contributing

Please see [Contributing](./CONTRIBUTING.md)

## Code of Conduct

This project and everyone participating in it is governed by the [Code of Conduct listed here](./CODE-OF-CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [conduct@open-network.dev](mailto:conduct@open-network.dev).

## Licence

This repository is licensed under the [MIT](https://choosealicense.com/licenses/mit/) license.
npm package: @openneuro/cli
Description: OpenNeuro command line uploader / editor.
Author: Squishymedia
Latest version: 4.30.2
Deprecated: These tools are deprecated with OpenNeuro 4.30.0. See https://jsr.io/@openneuro/cli for the new command line tools.

---
name: Command Line Interface
route: /cli
---

# OpenNeuro command line interface

This tool allows you to upload and download [OpenNeuro.org](https://openneuro.org) datasets without a browser.

## Install

1. Install [Node.js](https://nodejs.org) (version 18 or higher)
2. In a terminal type: `npm install -g @openneuro/cli`

If you are using [yarn](https://yarnpkg.com/) you can also perform the installation with `yarn global add @openneuro/cli`
(make sure the installation folder is part of your `PATH` by adding `export PATH="$(yarn global bin):$PATH"` to `~/.bashrc`)

## Setup

The setup step is needed for both uploading _and_ downloading data from OpenNeuro.

Run `openneuro login` to configure credentials.
This prompts you for the required configuration fields and saves this to `.openneuro` in your home directory or profile.
`openneuro login` will require you to enter an API key.
You can obtain an API key via a browser at https://openneuro.org/keygen after logging to the OpenNeuro platform via one of the provided authentication services (for example ORCID).

After successfully running `openneuro login`, you can manually configure custom servers by editing the `.openneuro` file.

## Usage

### Uploading datasets

To upload a new dataset:

`openneuro upload <dataset directory>`

Your dataset must pass validation to upload but warnings can be skipped with `openneuro upload -i <dataset directory>`. A default label is set using the directory name.

To resume an interrupted upload or add files to an existing dataset:

`openneuro upload --dataset <accession number> <dataset directory>`

where <accession_number> is a unique dataset identifier that can be found in the URL. For example accession number for `https://openneuro.org/datasets/ds001555` is `ds001555`.

This command will add or replace any files in the dataset but does not delete any files that are only present in the server copy of the dataset.

### Downloading datasets

To download a snapshot:

`openneuro download <accession number> <destination directory>`

To download the current draft files:

`openneuro download --draft <accession number> <destination directory>`

If the destination directory does not exist, it will be created. Any files from the dataset that are already present in the directory will be skipped, allowing you to resume an interrupted download.

## Errors

Package: OpenNeuro CLI download option

Issue: `TypeError: path must be a string or Buffer`

Solution: This error is due to a failure to read the `~/.openneuro` configuration file.
This file can be created with the command `openneuro login`, see the "Setup" step above.
npm package: @opennextjs/cloudflare
Description: Cloudflare builder for next apps
Latest version: 1.19.1

# OpenNext for Cloudflare

Deploy Next.js apps to Cloudflare!

[OpenNext for Cloudflare](https://opennext.js.org/cloudflare) is a Cloudflare specific adapter that enables deployment of Next.js applications to Cloudflare.

## Get started

To get started with the adapter visit the [official get started documentation](https://opennext.js.org/cloudflare/get-started).

## Local development

- you can use the regular `next` CLI to start the Next.js dev server:

## Local preview

Run the following commands to preview the production build of your application locally:

- build the app and adapt it for Cloudflare

  ```bash
  npx opennextjs-cloudflare build
  # or
  pnpm opennextjs-cloudflare build
  # or
  yarn opennextjs-cloudflare build
  # or
  bun opennextjs-cloudflare build
  ```

- Preview the app in Wrangler

  ```bash
  npx wrangler dev
  # or
  pnpm wrangler dev
  # or
  yarn wrangler dev
  # or
  bun wrangler dev
  ```

## Deploy your app

Deploy your application to production with the following:

- build the app and adapt it for Cloudflare

  ```bash
  npx opennextjs-cloudflare build && npx opennextjs-cloudflare deploy
  # or
  pnpm opennextjs-cloudflare build && pnpm opennextjs-cloudflare deploy
  # or
  yarn opennextjs-cloudflare build && yarn opennextjs-cloudflare deploy
  # or
  bun opennextjs-cloudflare build && bun opennextjs-cloudflare deploy
  ```