e89f2f4b7b
Created 10 detailed GitHub issues covering: - Project activation and management UI (#1-2) - Worker node coordination and visualization (#3-4) - Automated GitHub repository scanning (#5) - Intelligent model-to-issue matching (#6) - Multi-model task execution system (#7) - N8N workflow integration (#8) - Hive-Bzzz P2P bridge (#9) - Peer assistance protocol (#10) Each issue includes detailed specifications, acceptance criteria, technical implementation notes, and dependency mapping. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
20 lines
863 B
TypeScript
20 lines
863 B
TypeScript
import { PresetProperty } from 'storybook/internal/types';
|
|
|
|
declare const addons: PresetProperty<'addons'>;
|
|
declare const previewAnnotations: PresetProperty<'previewAnnotations'>;
|
|
/**
|
|
* Try to resolve react and react-dom from the root node_modules of the project addon-docs uses this
|
|
* to alias react and react-dom to the project's version when possible If the user doesn't have an
|
|
* explicit dependency on react this will return the existing values Which will be the versions
|
|
* shipped with addon-docs
|
|
*
|
|
* We do the exact same thing in the common preset, but that will fail in Yarn PnP because
|
|
*
|
|
* Storybook/internal/core-server doesn't have a peer dependency on react This will make
|
|
*
|
|
* @storybook/react projects work in Yarn PnP
|
|
*/
|
|
declare const resolvedReact: (existing: any) => Promise<any>;
|
|
|
|
export { addons, previewAnnotations, resolvedReact };
|