Results for flight-with-resources

A Flight mixin for sharing named resources between components.

Authentication and session helpers for using WorkOS & AuthKit with Next.js

Internal package to keep track of in-flight requests to Bugsnag

Node.js CORS middleware

Format numbers for human consumption.

React Server Components bindings for DOM using Webpack. This is intended to be integrated into meta-frameworks. It is not intended to be imported directly.

Flight: HashiCorp SVG icon set

A React + TypeScript porting of react-flight-indicators (https://github.com/skyhop/react-flight-indicators)

Topological sorting with grouping support

General purpose node utilities

JSON parse with prototype poisoning protection

Ensure all core dependencies are up to date before `npm start`

Sequential, diverging and categorical color schemes.

The Ember addon for the HashiCorp Flight SVG icon set

wait-on is a cross platform command line utility and Node.js API which will wait for files, ports, sockets, and http(s) resources to become available

A collection of small async/await utilities

React Server Components bindings for DOM using Bun. This is intended to be integrated into meta-frameworks. It is not intended to be imported directly.

React Server Components bindings for DOM using Turbopack. This is intended to be integrated into meta-frameworks. It is not intended to be imported directly.

Phase 3 of the catalog plane. The flights vertical is a partial-adoption module for live-API flight supplier search and booking in OTA, tour-operator, and DMC deployments.

Welcome to your new Jetshop Flight shop! Here's some resources to help you getting started.

Node compatible event emitter with extra features

HTTP-friendly error objects

A tiny react-native module that lets you determine whether your app is running in TestFlight

Biome is a toolchain for the web: formatter, linter and more

Its primary purpose is to ensure that only one call to an expensive or duplicative operation is in flight at any given time. When multiple requests request the same resource, singleflight ensures that the function is executed only once, and the result is shared among all callers. This pattern is particularly useful in scenarios where caching isn't suitable or when the results are expected to change frequently.