Docs: Migration guide could reference AST-based tooling for the textual search step

[flaglint]

Your LaunchDarkly → OpenFeature migration guide at
docs.flipt.io/v1/guides/migration/launchdarkly/openfeature is the
most thorough one I've found for Node.js teams.

One step that caught my attention:

"First, perform a textual search for node-server-sdk across
your project."

This works but misses aliased imports, CJS require patterns, and
the new @launchdarkly/node-server-sdk package name. It also doesn't
catch the argument-order difference between the two APIs:

ldClient.boolVariation(key, context, fallback)
openFeatureClient.getBooleanValue(key, fallback, context)

A grep-based migration silently swaps fallback and context in
production. Nothing looks wrong in code review.

I built an open-source CLI called FlagLint that handles this with
AST analysis — it finds every direct LD SDK call, generates
reviewable migration diffs with correct argument-order handling,
and flags dynamic keys and bulk calls for manual review.

npx flaglint scan ./src — free, MIT, Node.js 20+.

Would you consider adding a note in the "Find where in your code
base the LaunchDarkly SDK is used" section pointing to this as an
alternative to manual search?

https://github.com/flaglint/flaglint
https://flaglint.dev

[markphelps]

@flaglint looks like a cool tool. feel free to open a PR on the docs repo https://github.com/flipt-io/docs/pulls