Skip to content
FlagLint

Enterprise Demo

The enterprise checkout-service demo shows a fictional mid-sized SaaS company standardizing several Node.js services on OpenFeature while keeping LaunchDarkly as the provider.

Source: examples/enterprise-checkout-service

What It Demonstrates

Section titled “What It Demonstrates”
  • boolVariation, stringVariation, numberVariation, and jsonVariation.
  • Shared OpenFeature client imports.
  • Dynamic keys requiring manual review.
  • Detail evaluations requiring manual review.
  • Provider/bootstrap files excluded from policy enforcement.
  • Completed-state validation that scans real files and passes.

Contributor-Mode Commands

Section titled “Contributor-Mode Commands”

From the repository root:

Terminal window
npm install
npm run build

Generate inventory:

Terminal window
node ./dist/bin/flaglint.js scan \
  ./examples/enterprise-checkout-service/src \
  --config ./examples/enterprise-checkout-service/.flaglintrc \
  --format html \
  --output report.html

Preview migration:

Terminal window
node ./dist/bin/flaglint.js migrate \
  ./examples/enterprise-checkout-service/src \
  --config ./examples/enterprise-checkout-service/.flaglintrc \
  --dry-run

Validate the completed state:

Terminal window
node ./dist/bin/flaglint.js validate \
  ./examples/enterprise-checkout-service/after-complete \
  --no-direct-launchdarkly \
  --config ./examples/enterprise-checkout-service/.flaglintrc

Expected output:

- Scanning ./examples/enterprise-checkout-service/after-complete...
✓ validate --no-direct-launchdarkly: no direct LaunchDarkly evaluation calls found.
  Scanned 5 file(s).

Production Use

Section titled “Production Use”

Use the published package after the release that contains the documented capability:

Terminal window
npx flaglint scan ./src
npx flaglint migrate ./src --dry-run
npx flaglint validate ./src --no-direct-launchdarkly

Feedback

Section titled “Feedback”