dfrtz

/**
 * @file Utilities for running Pandas queries against a Javascript dataset.
 *
 * @summary Pandas query utilities.
 *
 * @version 1.0.0
 *
 * @author David Fritz
 * @copyright 2025 David Fritz
 * @license MIT

dfrtz

/**
 * @file Utilities for running Python in a background browser thread using Pyodide (WebAssembly).
 *
 * @summary Python WebWorker runner utilities.
 *
 * @version 1.0.0
 *
 * @author David Fritz
 * @copyright 2025 David Fritz
 * @license MIT

dfrtz

/**
 * @file Utilities for running DuckDB queries against a Javascript dataset.
 *
 * @summary DuckDB query utilities.
 *
 * @version 1.0.0
 *
 * @author David Fritz
 * @copyright 2025 David Fritz
 * @license MIT

dfrtz

Plotly Dash Custom Table

100% JS alternative to Plotly Dash DataTable, with full control over filtering and formatting.

Uses standard HTML component trees, MATCH based callbacks, and dash_clientside to perform the same behaviors (and more) without any Typescript or custom React components. The tree can be created in Python or Javascript, as long as the required components are added.

Also provides a general example for other custom "State" type classes that can be used to make Javascript based components without an NPM setup.

dfrtz

Plotly Dash Clientside Components

Basic library and example of how to create Plotly Dash components in clientside operations.

How To

1. Save the dashx.js file to assets/dashx.js, or a custom asset location.
2. Return components from JS calls similar to Python components. e.g. Dash.html.Div({children: "Hello World!"})

Full example

dfrtz

/**
 * @file A collection of global library functions used for similar functionality across JS and Python.
 *
 * @summary Javascript helpers for common Python actions.
 *
 * @author David Fritz
 * @version 1.0.0
 *
 * @copyright 2024 David Fritz
 * @license MIT

dfrtz

#!/bin/bash

# Load configuration files from cloud services, such as AWS and GCP.

# Available config ENV variables:
#   AWS_SECRETS_TO_CONFIGS
#   GCP_SECRETS_TO_CONFIGS
#
# Set secrets to load as configs with the following format:
#   <ENV key>="<secret1>:<file1>,<secret2>:<file2>,..."