Skip to main content

lfx-bundles

The long tail of Langflow's provider components as a single manifest-less metapackage, modeled on langchain-community. This is the destination for every vendor/third-party provider that does not warrant its own standalone distribution; the curated partner providers (OpenAI, Anthropic, AWS, DataStax, Cohere) ship as separate lfx-<provider> packages instead.

How it works

lfx-bundles declares the lfx.bundles entry point:

[project.entry-points."lfx.bundles"]
lfx_bundles = "lfx_bundles"

At startup, lfx resolves this package and folder-walks its immediate subdirectories. Each subdirectory is one bundle, registered at the @official slot under its directory name — no extension.json, no per-provider manifest. Adding a provider is just adding a folder.

src/lfx_bundles/
├── __init__.py        # bare namespace marker
├── <provider>/        # one bundle, e.g. tavily/, pinecone/, ...
│   └── *.py           # Component subclasses
└── ...

A component's identity is its bundle name (ext:<provider>:<Class>@official), which is stable whether the provider ships here or graduates to a standalone lfx-<provider> package. Because a manifest-shipping package always shadows the manifest-less metapackage, a provider can graduate with no lockstep release.

Installing

pip install langflow                   # full provider set, torch-free (langflow pins lfx-bundles[all-no-torch]; use [all] for cuga/codeagents)
pip install lfx                        # engine only, no bundles
pip install "lfx[bundles]"             # engine + this metapackage (deployment footnote)
pip install "lfx-bundles[<provider>]"  # one provider's code + that provider's SDK deps

lfx-bundles itself depends only on lfx. Each provider's third-party SDKs are optional extras (PEP 685-normalized keys, e.g. lfx-bundles[google]); the generated all extra pulls every provider's deps and is what langflow depends on, so pip install langflow is unchanged.

Adding a provider

Providers are moved here by scripts/migrate/consolidate_bundles.py, which also maintains the per-provider extras and the generated all aggregate. Do not hand-edit the extras block in pyproject.toml. Provider folder names must be lowercase snake_case (a-z, 0-9, _, 2–64 chars).

Metadata

Release files for lfx-bundles 1.1.19

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for lfx-bundles 1.1.19
File Interpreter ABI Platform
lfx_bundles-1.1.19-py3-none-any.whl Python 3 none any Details

Release files / lfx_bundles-1.1.19-py3-none-any.whl

Download URL lfx_bundles-1.1.19-py3-none-any.whl
Size 357.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
99835298af2630136ac9cbc33496d990e4245be000a0ec3746b3e57a18340bea
BLAKE2b-256 checksum
How to use checksums
a5ba5f234354761ccf439d426440a2a7d59b3b223d67025992f739884535d82f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.8 {"installer":{"name":"uv","version":"0.12.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page