fix(storybook): handle inherited config correctly when identifying the framework used for inferred tasks

[leosvelperez]

Current Behavior

When inferring Storybook tasks and identifying the framework used in the Storybook configuration, the project .storybook/main.{js|ts} file is scanned using AST to get the framework property. This doesn't account for the framework to have been defined in a base/parent configuration file that's merged into the project Storybook configuration. Therefore, the framework is not correctly identified in such cases.

Expected Behavior

When inferring Storybook tasks, the framework should be correctly identified regardless of where it was defined (project config or base/parent config).

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Apr 23, 2024 0:00am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 2476a9a. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --targets=e2e,e2e-ci --base=3d9bd16ce0f322e28e082bbb09f73069310ed6f2 --head=2476a9a2849adf954eb7bd2efa0bc9c45aa15912 --parallel=1
• nx affected --targets=lint,test,build --base=3d9bd16ce0f322e28e082bbb09f73069310ed6f2 --head=2476a9a2849adf954eb7bd2efa0bc9c45aa15912 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=3d9bd16ce0f322e28e082bbb09f73069310ed6f2 --head=2476a9a2849adf954eb7bd2efa0bc9c45aa15912
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=3d9bd16ce0f322e28e082bbb09f73069310ed6f2 --head=2476a9a2849adf954eb7bd2efa0bc9c45aa15912

---

Sent with 💌 from NxCloud.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.