OpenFeature provider support

[gustavohstrassburger]

Tracking issue for official OpenFeature support in the JavaScript SDKs — split out from the umbrella request PostHog/posthog#9609.

Status

• 🚧 Provider PR open: feat: add official PostHog OpenFeature server provider (Node) #3994 — adds two runtime-specific packages:
  • @posthog/openfeature-node-provider (OpenFeature server SDK, wraps posthog-node)
  • @posthog/openfeature-web-provider (OpenFeature web SDK, wraps posthog-js)
• 🚧 Docs PR open: Add OpenFeature (JavaScript) feature flags provider docs posthog.com#18105

Related

• I would like to donate the PostHog OpenFeature provider #2139 — community offer to donate an existing PostHog OpenFeature provider

Umbrella issue: PostHog/posthog#9609

[github-actions]

AI triage for #4051

Conclusion: Valid feature tracking issue; keep open and labeled for feature flags.
Confidence: 89%
Suggested labels: enhancement, feature/flags, team/feature-flags

Thanks for tracking this. This looks correctly scoped as a feature request for official OpenFeature provider support. Since the issue already points to the implementation PR (#3994) and docs PR, I’d keep this open until the provider packages and documentation are merged/released.

Investigation

• The issue is explicitly a tracking issue for official OpenFeature support and lists proposed runtime-specific packages for Node and web providers.
• A repository search for OpenFeature-related package names in the current checkout did not find existing OpenFeature provider packages under packages/.
• pnpm-workspace.yaml includes packages/*, so adding new provider packages under packages/ would fit the existing workspace structure.
• The existing labels enhancement, feature/flags, and team/feature-flags match the request type and owning area.

Relevant files: packages/, pnpm-workspace.yaml, package.json

Fix assessment

• Straightforward: no
• Risk: medium
• Reason: This is not a small isolated fix: it introduces official provider packages for multiple runtimes and likely requires API design, tests, package configuration, release setup, and documentation. The issue also references an existing implementation PR.

Fix PR skipped: feature requests require an explicit trusted fix command or mode: fix before opening a draft PR

Close proposal

None. No issue close action was taken.

---

Generated by posthog-watcher-action using pi.