open-index/open-npm huggingface dataset:
npm package: @stanfordspezi/spezi-firebase-utils
Description: Utility functions for Firebase projects
Author: Stanford Mussallem Center for Biodesign
Latest version: 0.1.15

<!--

This source file is part of the Stanford Biodesign Digital Health Spezi Firebase open-source project

SPDX-FileCopyrightText: 2025 Stanford University and the project authors (see CONTRIBUTORS.md)

SPDX-License-Identifier: MIT

-->

# Spezi Firebase Utils

[![Build and Test](https://github.com/StanfordSpezi/spezi-firebase/actions/workflows/build-and-test.yml/badge.svg)](https://github.com/StanfordSpezi/spezi-firebase/actions/workflows/build-and-test.yml)
[![codecov](https://codecov.io/gh/StanfordSpezi/spezi-firebase/graph/badge.svg)](https://codecov.io/gh/StanfordSpezi/spezi-firebase)

A collection of utility functions for Firebase projects, extracted from the Stanford ENGAGE-HF project. This package provides core utilities used by other Spezi Firebase packages.

## Installation

```bash
npm install @stanfordspezi/spezi-firebase-utils
```

## Features

- **Schema Converters**: Type-safe data conversion with Zod
- **Localization**: Easily handle multi-language text with fallbacks
- **Array Helpers**: Functions for working with arrays (average, median, percentile, etc.)
- **Date Utilities**: Simple date manipulation functions
- **Lazy Loading**: Generic lazy initialization pattern

## Usage Examples

### Schema Converter

```typescript
import { SchemaConverter } from '@stanfordspezi/spezi-firebase-utils'
import { z } from 'zod'

const userSchema = z.object({
  name: z.string(),
  email: z.string().email(),
  age: z.number().optional(),
})

const userConverter = new SchemaConverter({
  schema: userSchema,
  encode: (user) => ({
    name: user.name,
    email: user.email,
    age: user.age,
  }),
})
```

### Localized Text

```typescript
import { LocalizedText } from '@stanfordspezi/spezi-firebase-utils'

const greeting = new LocalizedText({
  en: 'Hello',
  es: 'Hola',
  fr: 'Bonjour',
})

console.log(greeting.localize('fr')) // 'Bonjour'
console.log(greeting.localize('de', 'en')) // 'Hello' (fallback)
```

## License

This project is licensed under the MIT License. See [Licenses](https://github.com/StanfordSpezi/spezi-firebase/tree/main/LICENSES) for more information.

## Contributors

This project is developed as part of the Stanford Mussallem Center for Biodesign at Stanford University.
See [CONTRIBUTORS.md](https://github.com/StanfordSpezi/spezi-firebase/tree/main/CONTRIBUTORS.md) for a full list of all Spezi Firebase contributors.

![Stanford Mussallem Center for Biodesign Logo](https://raw.githubusercontent.com/StanfordBDHG/.github/main/assets/biodesign-footer-light.png#gh-light-mode-only)
![Stanford Mussallem Center for Biodesign Logo](https://raw.githubusercontent.com/StanfordBDHG/.github/main/assets/biodesign-footer-dark.png#gh-dark-mode-only)
npm package: @stangres/react-leaflet
Description: React components for Leaflet maps
Author: Alex N
Latest version: 2.8.0

# React-Leaflet 
[![npm version](https://img.shields.io/npm/v/@stangres/react-leaflet.svg)](https://www.npmjs.com/package/@stangres/react-leaflet)

This is literally just a fork of [react-leaflet](https://github.com/PaulLeCam/react-leaflet) that adds the ability to directly extend components. Unless you have an issue specifically about extending components DO NOT raise issues here. Raise them on the [react-leaflet](https://github.com/PaulLeCam/react-leaflet/issues) repository.

This repository exists because of https://github.com/PaulLeCam/react-leaflet/issues/506

Please read through that issue before deciding if you actually should use this library and not react-leaflet. For most use cases react-leaflet will be fine.

TLDR;
react-leaflet v2 makes it impossible to directly extend these components:

- AttributionControl
- Circle
- ExtendableCircle
- FeatureGroup
- GeoJSON
- ImageOverlay
- LayerGroup
- LayersControl
- Marker
- Pane
- Polygon
- Polyline
- Popup
- Rectangle
- ScaleControl
- SVGOverlay
- TileLayer
- Tooltip
- VideoOverlay
- WMSTileLayer
- ZoomControl

This fork lets you extend those.

The extendable exports of these components are all formatted like: `Extendable<COMPONENT>`

e.g. `ExtendableAttributionControl`, `ExtendableCircle`, etc...

## Usage
```javascript
import { ExtendableTileLayer, withLeaflet } from '@stangres/react-leaflet'

class MyCustomTileLayer extends ExtendableTileLayer {
    // Go nuts here
}
export default withLeaflet(MyCustomTileLayer)
```

## License

MIT\
See [LICENSE](LICENSE) file.
npm package: @stanholub/nimble-js
Description: A frontend framework to make the frontend great again.
Latest version: 1.0.0

# nimble

## Commands

This package has the following commands:

- `npm run build` - Bundle the project into a single ESM file
- `npm run lint` - Lint the project
- `npm run lint:fix` - Lint the project and fix any issues
- `npm run test [<test-path>]` - Start the test runner in watch mode
- `npm run test:run [<test-path>]` - Run the tests once
npm package: @stankng/components
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.0.5.
Author: Kyle Stankovich
Latest version: 0.0.1

# Components

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test components` 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: @stankng/services
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.0.5.
Author: Kyle Stankovich
Latest version: 0.0.1

# Services

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test services` 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: @stankng/utils
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 12.0.5.
Author: Kyle Stankovich
Latest version: 0.0.1

# Utils

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test utils` 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.