chore: add missing dependencies

[43081j]

Adds a few missing dependencies which were previously picked up thanks to sibling monorepo packages having the same dependency.

cc @webpro

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

Basically ensure the build still succeeds.

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

Greptile Summary

Updates package.json files across multiple Storybook packages to explicitly declare dependencies that were previously being implicitly inherited from sibling packages in the monorepo.

• Added @types/estree to svelte-vite package for ESTree AST type definitions
• Added @babel/core to both create-react-app preset and react renderer packages
• Added expect-type v1.1.0 to vue3 and react renderer packages
• Added browser-assert and expect-type to core package
• Added @babel/types to vitest addon package

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

[greptile-apps]

LGTM

_{6 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

LGTM

_{6 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}

[webpro]

Maybe what we could consider and investigate is remove more dependencies from code/package.json to make packages more self-contained. Then Knip can detect them properly as well. pnpm would help here too.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 3be46b4.

Command	Status	Duration	Result
nx run-many -t build --parallel=3	✅ Succeeded	1m 43s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-05-02 10:07:41 UTC

[43081j]

knip is already detecting this, isn't it? 👀

I thought that's how we got the warnings before. it detected that the sub-packages didn't have the right dependencies, even though code/ did

maybe I'm mistaken :D

[webpro]

lol yes I forgot about strict mode, and didn't use that in my latest PR here unfortunately. Comes with more strictness, isolated packages should probably be separate flag. So many projects, so many setups.