Angular: Add an in-process docgen analyzer, replacing Compodoc under the flag by valentinpalkovic · Pull Request #35805 · storybookjs/storybook

valentinpalkovic · 2026-08-07T18:26:24Z

What I did

Angular is the only framework whose docgen needs a second tool. Under experimentalDocgenServer, Storybook shells out to Compodoc, which re-parses the whole project and writes a documentation.json. That is where the Angular server-docgen path spends its time, and it is why a one-line edit costs about as much as a cold start.

This adds AngularComponentMetaManager, an in-process analyzer that reads component metadata straight from TypeScript sources through a warm LanguageService, one per matched tsconfig. Under the flag it powers docgen end to end and Compodoc is not on that pipeline at all. With the flag off nothing changes: Compodoc still writes documentation.json and still powers the controls in the preview.

                       ┌─ Compodoc ──── documentation.json ──┐
 *.component.ts ───────┤   (flag off, browser)               ├──► extract-arg-types ──► argTypes
                       └─ AngularComponentMetaManager ───────┘        one conversion
                           (flag on, Node worker)
                           warm LanguageService per tsconfig

The analyzer emits the same Compodoc-JSON subset the existing conversion already consumes, so there is still one conversion with two producers. That was the design constraint: no second argTypes implementation to keep in sync.

What it produces

Given this component:

export type BadgeSize = 'small' | 'medium' | 'large';

@Component({ selector: 'sb-badge', template: '' })
export class BadgeComponent {
  /** Controls the badge footprint. */
  @Input() size: BadgeSize = 'medium';

  /** Emitted when the badge is dismissed. */
  @Output() dismissed = new EventEmitter<string>();
}

the analyzer emits the Compodoc-JSON subset (trimmed to the two members):

{
  "name": "BadgeComponent",
  "type": "component",
  "selector": "sb-badge",
  "inputsClass": [
    {
      "name": "size",
      "type": "BadgeSize",
      "optional": false,
      "defaultValue": "'medium'",
      "description": "Controls the badge footprint."
    }
  ],
  "outputsClass": [
    {
      "name": "dismissed",
      "type": "EventEmitter",
      "defaultValue": "new EventEmitter<string>()",
      "description": "Emitted when the badge is dismissed."
    }
  ]
}

and the shared conversion turns that into argTypes. size resolves through the alias to its literals, which is what makes it a radio group rather than a text field:

{
  "size": {
    "name": "size",
    "description": "Controls the badge footprint.",
    "type": { "name": "enum", "value": ["small", "medium", "large"] },
    "table": {
      "category": "inputs",
      "type": { "summary": "BadgeSize", "required": true },
      "defaultValue": { "summary": "medium" }
    }
  },
  "dismissed": {
    "name": "dismissed",
    "type": { "name": "other", "value": "void" },
    "action": "dismissed",
    "table": { "category": "outputs", "type": { "summary": "EventEmitter", "required": true } }
  }
}

Performance

Full profile, 6 repetitions, generated Angular project, same machine:

	Compodoc	AngularComponentMeta
cold	393ms	142ms
warm (one file saved)	390ms	2ms
peak RSS	250.7MB	1.9MB

The cold number is like-for-like: 1300 documented members on both sides. The warm number is not a fair ratio and the harness says so in its own output - Compodoc re-documents all 1301 members on every save, the analyzer re-documents the 14 that changed. That difference is the point of the change, but it is not a 160x speedup of the same work.

Extraction freshness is scoped to the component's transitive import closure rather than to every file the project has ever cached. On a synthetic 2002-file project with 300 components that is the difference between 598,897 and 1,495 getModifiedTime calls, and it was about 97% of the extraction loop's wall time.

Reproduce with yarn workspace @storybook/docgen-harness bench:docgen-perf from the repo root. The methodology is in code/lib/docgen-harness/src/perf/PERF-METHODOLOGY.md.

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

yarn task sandbox --template angular-vite/docgen-server-ts --start-from auto
cd ../storybook-sandboxes/angular-vite-docgen-server-ts && yarn storybook
Open Example / Button → Docs. The props table should be grouped into PROPERTIES, INPUTS and OUTPUTS, with descriptions and defaults filled in:
- label is a string with default Button
- primary is a boolean with default false
- size renders as a radio group of small / medium / large, not a text field - that is the literal-union-to-enum rule shown above
- onClick sits under OUTPUTS with summary EventEmitter
With the dev server still running, add this to src/stories/button.component.ts and save:
```
/** Probe added to verify docgen hot updates. */
@Input() probe?: 'a' | 'b';
```
The table gains a probe row with that description and an a / b radio control, without a restart. That is the incremental watch; Compodoc would have re-parsed the project to answer the same question.
Set features.experimentalDocgenServer to false in .storybook/main.ts, restart, and confirm the Docs page is exactly what it is on next. Compodoc runs, the analyzer does not.

Note

Step 1 currently needs typescript@^6 in the sandbox: Compodoc 2 crashes on TypeScript 7, and a freshly generated Angular sandbox resolves TypeScript 7. The template pins it. This affects the flag-off path only, since the analyzer does not run Compodoc.

Documentation

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

The analyzer's limitations are documented next to the analyzer. Nothing here is user-facing yet: the flag is experimental.

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
Declare whether manual QA will be needed for this PR during the next release, through qa:needed or qa:skip
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.

The fixture suites prove the Angular extractor against components written to exercise it. They cannot catch what only shows up across a whole project: component name collisions, imports that resolve to the wrong file, components the tsconfig never covered. A static Storybook build under experimentalDocgenServer already writes one docgen payload per component. This reads that output, strips the parts that are machine-specific or engine-specific, and keeps the result in the repo so a provider change becomes a reviewable diff. Findings are split by severity: a regression means docgen got worse and wants a fix, a change means it moved without getting worse and is adopted by re-recording. Both fail the run. CI verifies after building any sandbox that has baselines committed, derived from what is on disk so adding a directory is all it takes to gate a template.

The recorded baselines are captured from this sandbox's static build, and that build only writes per-component docgen snapshots when both flags are on. Until now no sandbox turned server-side Angular docgen on, so nothing exercised it end to end in CI.

…lines The monorepo's shared template stories reference their component as `globalThis.__TEMPLATE_COMPONENTS__.*`, so there is no import to resolve and no scanned file to find. All 74 of them errored by construction, which says something about the template-story harness rather than about docgen, and they buried the components that carry real signal. The Angular recording goes from 111 components to 37: 30 documented, 7 Angular classes declared inline in story files.

Attaching a `message` listener to a worker re-references its port, so calling `unref()` before the listeners are on leaves the worker holding the event loop open. `build-storybook` finished its work and then hung indefinitely, which on CI showed up as a ten-minute no-output timeout rather than as a failure. Only reachable with experimentalDocgenServer enabled, which no sandbox did until now.

Turning the flags on for the existing Angular sandbox would have swapped what that sandbox guards, leaving today's browser docgen untested while the server path is still experimental. A separate template keeps both covered. Runs daily rather than on every PR: it doubles the Angular sandbox cost and the configuration it guards is not the shipping one yet. Marked in-development so CI generates it from scratch until it is published to the sandboxes repository.

The sandbox now exists on the sandboxes repository, so CI clones it like every other template instead of scaffolding it from scratch on each run.

The sandbox differs from `angular-vite/default-ts` only by two feature flags, so visual output is already covered there on every run and repeating it doubles the Angular cost for no extra signal. `test-runner` is skipped alongside it because the job list adds a test-runner job precisely when chromatic is skipped, so skipping only chromatic would have swapped one job for another rather than dropping one.

…lags There was a hardcoded default template in the recorder and a separate disk-existence check in the CI config, so three places had to agree on which sandboxes carry docgen baselines. Now the flags on the template definition are the only source: a sandbox that turns on server docgen is baselined, and one that does not is not. A flagged template with nothing recorded yet fails instead of skipping quietly, which is the case the disk check used to swallow.

The derivation is exercised by the recorder and the generated CI config, so the unit test was duplicating that. `enablesDocgenServer` goes back to module-private with it, since exporting it was only for the test. Also reframes the cadence TODO: after 11.0 the standard sandboxes ship the new docgen approach by default, so this template gets removed rather than promoted.

storybook-app-bot · 2026-08-07T18:38:12Z

Package Benchmarks

^{Commit: 6a36902, ran on 11 August 2026 at 13:39:43 UTC}

The following packages have significant changes to their size or dependencies:

`@storybook/angular-vite`

	Before	After	Difference
Dependency count	29	29	0
Self size	23.05 MB	23.00 MB	🎉 -49 KB 🎉
Dependency size	12.68 MB	12.68 MB	0 B
Bundle Size Analyzer	Link	Link

valentinpalkovic · 2026-08-07T18:44:25Z

Quick heads-up on the red test-storybooks-portable-react, so nobody spends time on it: it is not caused by this PR.

The failing step is Run Playwright E2E tests in the React portable-stories kitchen sink. #35803 is branched off next and contains none of this work, and the same job fails there in the same step:

	failing spec
this PR	`save-from-controls` - expected `"Copied …"`, got `"Global DecoratorUpdated …"`
#35803 (control, no changes from here)	`component-testing.spec.ts:450` - `expect(locator).toBeVisible()` timed out

Same job, same step, a different spec each time. That is a flaky suite rather than a deterministic break.

For what it is worth on the other side: this branch touches no file under test-storybooks/, and in code/renderers/react/ it only touches componentManifest/componentMeta/**, which portable stories never load.

normal-generated is red only because it aggregates that job. Everything Angular passed, including UI Tests: angular-vite/default-ts and both angular-cli-latest builders through create/dev/e2e/vitest/chromatic - which is the flag-off Compodoc path this PR must not disturb.

valentinpalkovic · 2026-08-07T18:45:02Z

@coderabbitai review

coderabbitai · 2026-08-07T18:45:08Z

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

valentinpalkovic · 2026-08-07T19:31:34Z

@coderabbitai full review

coderabbitai · 2026-08-07T19:31:40Z

⚠️ Action not completed

Review skipped: 222 files exceed the limit of 150.

Both the React and the Angular component-meta analyzers keep one TypeScript LanguageService per matched tsconfig, and both need the same thing from it: which files the project claims, what version each is on, when a change event invalidates a snapshot, and how to stay fresh when an edit races the debounced watcher. React had all of that inline. `ProjectFileTracker` owns it once. React loses about 150 lines of it and reads the same behaviour back; the Angular analyzer arriving next consumes it instead of writing a second copy. The tracker deliberately knows nothing about either renderer: it takes a structural `ProjectFileSystem` rather than importing `typescript`, so `typeof ts` satisfies it without core naming the package.

@output

Angular docgen goes through Compodoc, which shells out to a separate CLI, re-parses the whole project on every run and only reports what its own JSON schema can express. That is slow, hard to keep incremental, and loses type information the compiler already has. This adds @storybook/angular-cm, an analyzer that runs inside the Storybook process on a TypeScript LanguageService. It reads decorator and signal based inputs and outputs, follows inheritance across files, renders declared types through the checker, and carries JSDoc onto the members it emits. The manager keeps one project per tsconfig and reuses the service between runs so a file change re-checks only what it touched. The extraction rules here already include the corrections found by running the analyzer against real-world Angular repositories: ES-private and non-public DI members stay out of argTypes, import() qualifiers are stripped from rendered types, function members render their signature instead of a bare "function", accessor inputs keep their JSDoc tags, and getters carrying @output() are recognized.

Co-authored-by: Valentin Palkovic <dev@valentinpalkovic.dev>

The review suggestions were applied through the GitHub web editor, which left the closing `*/` of two shortened docblocks flush against the margin. oxfmt wants a leading space, so `format-check` failed on both files.

coderabbitai

Actionable comments posted: 1

🧹 Nitpick comments (1)

code/lib/angular-cm/src/analyzer/class-members.ts (1)
21-28: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Consider a locale-independent comparator for deterministic ordering.

localeCompare without an explicit locale depends on the host ICU data and locale environment. The emitted order feeds the committed argTypes baselines, so two machines can produce different member order for the same source. type-index.ts toMiscellaneous uses the same pattern.

If you want the order pinned across environments, pass a fixed locale or compare code units.
♻️ Proposed change
 function sortMembers(members: ClassMembers): void {
+  const collator = new Intl.Collator('en', { sensitivity: 'variant' });
   const byName = (a: MemberEntry<{ name: string }>, b: MemberEntry<{ name: string }>) =>
-    a.value.name.localeCompare(b.value.name);
+    collator.compare(a.value.name, b.value.name);
   members.inputs.sort(byName);
   members.outputs.sort(byName);
   members.properties.sort(byName);
   members.methods.sort(byName);
 }
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@code/lib/angular-cm/src/analyzer/class-members.ts` around lines 21 - 28,
Update the byName comparator in sortMembers to use a locale-independent,
deterministic name comparison, such as an explicit fixed locale or code-unit
ordering. Apply the same ordering fix to type-index.ts toMiscellaneous,
preserving the existing member sorting behavior.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@code/lib/angular-cm/src/analyzer/type-index.ts`:
- Around line 62-75: Update TypeIndex.render’s function/constructor type-node
branch to render typeNode.typeParameters and include the resulting generic
parameter list before the parameter list. Preserve the existing constructor
prefix, parameter rendering, and return-type rendering so types such as generic
function signatures retain valid metadata text.

---

Nitpick comments:
In `@code/lib/angular-cm/src/analyzer/class-members.ts`:
- Around line 21-28: Update the byName comparator in sortMembers to use a
locale-independent, deterministic name comparison, such as an explicit fixed
locale or code-unit ordering. Apply the same ordering fix to type-index.ts
toMiscellaneous, preserving the existing member sorting behavior.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 05fddd2a-e45a-42b7-8c28-e14bda94af17

📥 Commits

Reviewing files that changed from the base of the PR and between 8f5585f and afbe899.

⛔ Files ignored due to path filters (1)

yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (85)

code/core/src/common/utils/resolve-meta-component.test.ts
code/core/src/common/utils/resolve-meta-component.ts
code/core/src/component-meta/ComponentMetaManager.ts
code/core/src/component-meta/ProjectFileTracker.test.ts
code/core/src/component-meta/ProjectFileTracker.ts
code/core/src/component-meta/index.ts
code/core/src/component-meta/types.ts
code/core/src/shared/open-service/services/docgen/worker/docgen-worker-client.test.ts
code/core/src/shared/open-service/services/docgen/worker/docgen-worker-client.ts
code/frameworks/angular-vite/package.json
code/frameworks/angular-vite/src/compodoc-config.ts
code/frameworks/angular-vite/src/compodoc/ensure-documentation.ts
code/frameworks/angular-vite/src/docgen/build-docgen.integration.test.ts
code/frameworks/angular-vite/src/docgen/build-docgen.test.ts
code/frameworks/angular-vite/src/docgen/build-docgen.ts
code/frameworks/angular-vite/src/docgen/docgen-worker.test.ts
code/frameworks/angular-vite/src/docgen/docgen-worker.ts
code/frameworks/angular-vite/src/docgen/preset.test.ts
code/frameworks/angular-vite/src/docgen/preset.ts
code/frameworks/angular-vite/src/docgen/resolve-component.test.ts
code/frameworks/angular-vite/src/preset.ts
code/lib/angular-cm/README.md
code/lib/angular-cm/package.json
code/lib/angular-cm/src/analyzer/__testutils__/inline-source.ts
code/lib/angular-cm/src/analyzer/analyze-file.test.ts
code/lib/angular-cm/src/analyzer/analyze-file.ts
code/lib/angular-cm/src/analyzer/class-members.ts
code/lib/angular-cm/src/analyzer/context.ts
code/lib/angular-cm/src/analyzer/decorators.ts
code/lib/angular-cm/src/analyzer/inheritance.ts
code/lib/angular-cm/src/analyzer/jsdoc.ts
code/lib/angular-cm/src/analyzer/members.test.ts
code/lib/angular-cm/src/analyzer/members.ts
code/lib/angular-cm/src/analyzer/node-text.ts
code/lib/angular-cm/src/analyzer/signals.ts
code/lib/angular-cm/src/analyzer/type-index.ts
code/lib/angular-cm/src/extract-arg-types.ts
code/lib/angular-cm/src/index.ts
code/lib/angular-cm/src/manager.test.ts
code/lib/angular-cm/src/manager.ts
code/lib/angular-cm/src/project.ts
code/lib/angular-cm/src/types.ts
code/lib/angular-compodoc/README.md
code/lib/angular-compodoc/package.json
code/lib/angular-compodoc/src/compodoc-types.ts
code/lib/angular-compodoc/src/extract-arg-types.test.ts
code/lib/angular-compodoc/src/extract-arg-types.ts
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/example-button.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/example-header.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/example-page.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-argtypes-doc-button.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-argtypes-doc-directive.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-argtypes-doc-injectable.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-argtypes-doc-pipe.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-angular-forms-customcontrolvalueaccessor-custom-cva-component.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-complex-selectors-attribute-selectors-component.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-complex-selectors-class-selector-component.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-complex-selectors-multiple-class-selector-component.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-complex-selectors-multiple-selector-component.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-enums-enums-component.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-inheritance-base-button.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-inheritance-icon-button.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-ng-content-ng-content-about-parent.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-ng-on-destroy-component-with-on-destroy.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-on-push-on-push.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-pipe-custom-pipes.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-provider-di-component.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-template-template.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-without-selector-without-selector-ng-component-outlet.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-without-selector-without-selector.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-ng-module-import-module-chip.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-ng-module-import-module-for-root.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-ng-module-import-module.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-decorators-componentwrapperdecorator-decorators.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-decorators-theme-decorator-decorators.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-modulemetadata-in-export-default.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-modulemetadata-in-stories.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-modulemetadata-merge-default-and-story.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-styles-story-styles.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-others-app-initializer-use-factory.json
code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-others-issues-12009-unknown-component.json
code/lib/docgen-harness/src/sandbox-baselines/read-static-docgen.ts
code/playwright.config.ts
scripts/ci/sandboxes.ts
scripts/ci/utils/helpers.ts

💤 Files with no reviewable changes (15)

code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-ng-content-ng-content-about-parent.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-others-app-initializer-use-factory.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-pipe-custom-pipes.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-without-selector-without-selector-ng-component-outlet.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-template-template.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-ng-on-destroy-component-with-on-destroy.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-complex-selectors-class-selector-component.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-others-issues-12009-unknown-component.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-complex-selectors-multiple-selector-component.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-complex-selectors-attribute-selectors-component.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-decorators-componentwrapperdecorator-decorators.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/example-page.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-without-selector-without-selector.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/example-header.json
code/lib/docgen-harness/src/sandbox-baselines/baselines/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-complex-selectors-multiple-class-selector-component.json

🚧 Files skipped from review as they are similar to previous changes (21)

code/frameworks/angular-vite/package.json
code/frameworks/angular-vite/src/preset.ts
code/frameworks/angular-vite/src/compodoc/ensure-documentation.ts
code/frameworks/angular-vite/src/docgen/build-docgen.integration.test.ts
code/lib/angular-cm/src/manager.test.ts
code/frameworks/angular-vite/src/compodoc-config.ts
code/lib/angular-compodoc/package.json
code/lib/angular-compodoc/README.md
code/lib/angular-cm/src/manager.ts
code/lib/angular-cm/src/analyzer/analyze-file.ts
code/lib/angular-compodoc/src/extract-arg-types.test.ts
code/lib/angular-cm/src/analyzer/jsdoc.ts
code/core/src/common/utils/resolve-meta-component.ts
code/frameworks/angular-vite/src/docgen/resolve-component.test.ts
code/lib/angular-compodoc/src/compodoc-types.ts
code/lib/angular-compodoc/src/extract-arg-types.ts
code/core/src/shared/open-service/services/docgen/worker/docgen-worker-client.ts
code/lib/angular-cm/src/analyzer/members.test.ts
code/frameworks/angular-vite/src/docgen/build-docgen.ts
code/core/src/shared/open-service/services/docgen/worker/docgen-worker-client.test.ts
code/frameworks/angular-vite/src/docgen/build-docgen.test.ts

The review suggestion shortened this docblock through the GitHub web editor and dropped its closing `*/`, so the declaration below it became comment text: /** * Token standing in for the sandbox directory inside recorded strings. export const SANDBOX_TOKEN = '<sandbox>'; Still valid syntax, so lint and oxfmt passed and only `check` caught it: read-static-docgen.test.ts(6,10): error TS2305: Module has no exported member 'SANDBOX_TOKEN'. read-static-docgen.ts(43,29): error TS2304: Cannot find name 'SANDBOX_TOKEN'.

huang-julien

Tests and case coverage looks good to me :)

TypeIndex.render dropped typeNode.typeParameters, so <T>(value: T) => T rendered as (value: T) => T, an invalid type text in generated metadata.

…project' into HEAD # Conflicts: # code/core/src/component-meta/ProjectFileTracker.test.ts # code/core/src/component-meta/ProjectFileTracker.ts # code/core/src/component-meta/index.ts # code/core/src/shared/open-service/services/docgen/worker/docgen-worker-client.test.ts # code/core/src/shared/open-service/services/docgen/worker/docgen-worker-client.ts # code/lib/cli-storybook/src/sandbox-templates.ts # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/example-button.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/example-header.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/example-page.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-argtypes-doc-button.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-argtypes-doc-directive.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-argtypes-doc-injectable.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-argtypes-doc-pipe.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-angular-forms-customcontrolvalueaccessor-custom-cva-component.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-complex-selectors-attribute-selectors-component.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-complex-selectors-class-selector-component.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-complex-selectors-multiple-class-selector-component.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-complex-selectors-multiple-selector-component.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-enums-enums-component.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-inheritance-base-button.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-inheritance-icon-button.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-ng-content-ng-content-about-parent.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-ng-on-destroy-component-with-on-destroy.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-on-push-on-push.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-pipe-custom-pipes.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-provider-di-component.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-with-template-template.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-without-selector-without-selector-ng-component-outlet.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-component-without-selector-without-selector.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-ng-module-import-module-chip.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-ng-module-import-module-for-root.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-basics-ng-module-import-module.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-decorators-componentwrapperdecorator-decorators.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-decorators-theme-decorator-decorators.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-modulemetadata-in-export-default.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-modulemetadata-in-stories.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-modulemetadata-merge-default-and-story.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-core-styles-story-styles.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-others-app-initializer-use-factory.json # code/lib/docgen-harness/src/sandbox-baselines/__baselines__/angular-vite-docgen-server-ts/stories-frameworks-angular-vite-others-issues-12009-unknown-component.json # code/lib/docgen-harness/src/sandbox-baselines/read-static-docgen.ts # code/lib/docgen-harness/src/sandbox-baselines/run.ts # scripts/ci/utils/helpers.ts

…project' into HEAD

Matches React's ComponentMetaProject now that the base carries a Source type parameter.

Resolve the component-meta path-helper conflict: next moved normalizePath and isInNodeModules out of ProjectFileTracker into shared/utils/paths.ts (as slash and isInNodeModules). angular-cm now imports both from storybook/internal/common, which already re-exports that module.

coderabbitai

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

scripts/ci/utils/helpers.ts (1)
249-255: 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Disable the orb cache. cache-version: 'v4' only changes the cache key. Because with-cache defaults to true, the orb still restores and saves its node-deps-* cache alongside NODE_MODULES_CACHE_KEY. Set 'with-cache': false.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@scripts/ci/utils/helpers.ts` around lines 249 - 255, Disable the orb-managed
cache by setting its with-cache option to false in the relevant helper
configuration, while preserving the existing NODE_MODULES_CACHE_KEY handling and
yarn install behavior.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@scripts/ci/utils/helpers.ts`:
- Around line 249-255: Disable the orb-managed cache by setting its with-cache
option to false in the relevant helper configuration, while preserving the
existing NODE_MODULES_CACHE_KEY handling and yarn install behavior.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 691ebd37-8451-413a-92eb-1dcd561d2557

📥 Commits

Reviewing files that changed from the base of the PR and between afbe899 and 6a36902.

📒 Files selected for processing (6)

code/core/src/component-meta/ComponentMetaManager.ts
code/core/src/shared/open-service/services/docgen/worker/docgen-worker-client.test.ts
code/lib/angular-cm/src/analyzer/type-index.ts
code/lib/angular-cm/src/project.ts
code/lib/docgen-harness/src/sandbox-baselines/read-static-docgen.ts
scripts/ci/utils/helpers.ts

🚧 Files skipped from review as they are similar to previous changes (5)

code/lib/docgen-harness/src/sandbox-baselines/read-static-docgen.ts
code/core/src/component-meta/ComponentMetaManager.ts
code/core/src/shared/open-service/services/docgen/worker/docgen-worker-client.test.ts
code/lib/angular-cm/src/project.ts
code/lib/angular-cm/src/analyzer/type-index.ts

## Dependency Updates | Package | From | To | Type | | --- | --- | --- | --- | | `storybook` | 10.5.10 | 10.6.0 | minor | ## Release Notes <details> <summary><b>storybook</b> (10.5.10 → 10.6.0)</summary> ## 10.6.0 > New skills architecture for agentic workflows Storybook 10.6 contains hundreds of fixes and improvements: - 💻 CLI bindings for agent tools/skills - 🅰️ Angular-Vite MCP/skills support and improved docgen/snippets (experimental) - 🟢 Vue MCP/skills support and improved docgen/snippets (experimental) - 🧩 Tanstack / NextJS-Vite framework bugfixes - ⚡ Improved performance and reduced bundle size <details> <summary>List of all updates</summary> - Addon MCP: Stop silently dropping composed refs from MCP composition - [#36077](storybookjs/storybook#36077), thanks @kasperpeulen! - Addon Vitest: Pin storybook/test in optimizeDeps so its CJS-only deps are prebundled - [#35572](storybookjs/storybook#35572), thanks @Nic-Polumeyv! - Addon Vitest: Report test runs with failures as failed tool outcomes - [#36080](storybookjs/storybook#36080), thanks @kasperpeulen! - Addon Vitest: Resolve story test globs against the project root - [#36103](storybookjs/storybook#36103), thanks @kasperpeulen! - Addon-vitest: Filter Storybook instrumentation from reported stack traces - [#36120](storybookjs/storybook#36120), thanks @ghengeveld! - Angular Vite: Resolve tsConfig against the workspace root - [#36026](storybookjs/storybook#36026), thanks @ndelangen! - Angular-Vite: Run Compodoc on demand - [#35776](storybookjs/storybook#35776), thanks @valentinpalkovic! - Angular: Add an in-process docgen analyzer, replacing Compodoc under the flag - [#35805](storybookjs/storybook#35805), thanks @valentinpalkovic! - Angular: Bind only what the component accepts in story snippets, and report the rest - [#35943](storybookjs/storybook#35943), thanks @valentinpalkovic! - Angular: Decide the migration\'s zone.js import from the dependency tree - [#36008](https://github.com/story …[full notes](https://github.com/storybookjs/storybook/releases/tag/v10.6.0) </details> --- *This PR was auto-generated by [catalog-update-action](https://github.com/brandhaug/catalog-update-action).* Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

## Dependency Updates | Package | From | To | Type | | --- | --- | --- | --- | | `@storybook/react-vite` | 10.5.10 | 10.6.0 | minor | ## Release Notes <details> <summary><b>@storybook/react-vite</b> (10.5.10 → 10.6.0)</summary> ## 10.6.0 > New skills architecture for agentic workflows Storybook 10.6 contains hundreds of fixes and improvements: - 💻 CLI bindings for agent tools/skills - 🅰️ Angular-Vite MCP/skills support and improved docgen/snippets (experimental) - 🟢 Vue MCP/skills support and improved docgen/snippets (experimental) - 🧩 Tanstack / NextJS-Vite framework bugfixes - ⚡ Improved performance and reduced bundle size <details> <summary>List of all updates</summary> - Addon MCP: Stop silently dropping composed refs from MCP composition - [#36077](storybookjs/storybook#36077), thanks @kasperpeulen! - Addon Vitest: Pin storybook/test in optimizeDeps so its CJS-only deps are prebundled - [#35572](storybookjs/storybook#35572), thanks @Nic-Polumeyv! - Addon Vitest: Report test runs with failures as failed tool outcomes - [#36080](storybookjs/storybook#36080), thanks @kasperpeulen! - Addon Vitest: Resolve story test globs against the project root - [#36103](storybookjs/storybook#36103), thanks @kasperpeulen! - Addon-vitest: Filter Storybook instrumentation from reported stack traces - [#36120](storybookjs/storybook#36120), thanks @ghengeveld! - Angular Vite: Resolve tsConfig against the workspace root - [#36026](storybookjs/storybook#36026), thanks @ndelangen! - Angular-Vite: Run Compodoc on demand - [#35776](storybookjs/storybook#35776), thanks @valentinpalkovic! - Angular: Add an in-process docgen analyzer, replacing Compodoc under the flag - [#35805](storybookjs/storybook#35805), thanks @valentinpalkovic! - Angular: Bind only what the component accepts in story snippets, and report the rest - [#35943](storybookjs/storybook#35943), thanks @valentinpalkovic! - Angular: Decide the migration\'s zone.js import from the dependency tree - [#36008](https://github.com/story …[full notes](https://github.com/storybookjs/storybook/releases/tag/v10.6.0) </details> --- *This PR was auto-generated by [catalog-update-action](https://github.com/brandhaug/catalog-update-action).* Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Valentin Palkovic and others added 10 commits August 6, 2026 09:42

build(angular): publish the server docgen sandbox

c96a010

The sandbox now exists on the sandboxes repository, so CI clones it like every other template instead of scaffolding it from scratch on each run.

Merge branch 'next' into valentin/sb11-angular-docgen-sandbox-baselines

b46845d

valentinpalkovic added feature request ci:normal Run our default set of CI jobs (choose this for most PRs). qa:needed Pull Requests that will need manual QA prior to release. labels Aug 7, 2026

valentinpalkovic mentioned this pull request Aug 7, 2026

Angular: Generate static template snippets on the server #35796

Closed

3 of 9 tasks

valentinpalkovic added 4 commits August 7, 2026 22:06

Merge branch 'next' into valentin/angular-component-meta

dbd6dbb

Merge branch 'next' into valentin/sb11-angular-docgen-sandbox-baselines

32beffc

valentinpalkovic force-pushed the valentin/angular-component-meta branch from 6ce2dbc to b9fc3bd Compare August 7, 2026 20:27

valentinpalkovic changed the base branch from next to valentin/component-meta-project-tracker August 7, 2026 20:27

valentinpalkovic requested review from jonniebigodes and kylegach as code owners August 7, 2026 20:27

This was referenced Aug 7, 2026

Angular: Record per-component docgen baselines from built sandboxes #35750

Merged

Core: Move the component-meta invalidation state machine into core #35806

Merged

valentinpalkovic commented Aug 10, 2026

View reviewed changes

Comment thread scripts/ci/sandboxes.ts Outdated

Apply suggestions from code review

afbe899

Co-authored-by: Valentin Palkovic <dev@valentinpalkovic.dev>

valentinpalkovic marked this pull request as ready for review August 10, 2026 11:19

Build: Restore the JSDoc spacing oxfmt expects

51cfc9d

The review suggestions were applied through the GitHub web editor, which left the closing `*/` of two shortened docblocks flush against the margin. oxfmt wants a leading space, so `format-check` failed on both files.

coderabbitai Bot reviewed Aug 10, 2026

View reviewed changes

Comment thread code/lib/angular-cm/src/analyzer/type-index.ts Outdated

coderabbitai Bot mentioned this pull request Aug 10, 2026

Harness: Measure the Angular component meta analyzer against Compodoc #35832

Closed

1 of 9 tasks

huang-julien approved these changes Aug 10, 2026

View reviewed changes

valentinpalkovic added 4 commits August 11, 2026 12:45

Angular: Render generic type parameters on function/constructor types

3ab7fec

TypeIndex.render dropped typeNode.typeParameters, so <T>(value: T) => T rendered as (value: T) => T, an invalid type text in generated metadata.

Merge remote-tracking branch 'origin/valentin/component-meta-program-…

ea57253

…project' into HEAD

Angular: Instantiate ProgramBackedProject's Source with ts.SourceFile

aa77f4d

Matches React's ComponentMetaProject now that the base carries a Source type parameter.

Base automatically changed from valentin/component-meta-program-project to next August 11, 2026 13:21

coderabbitai Bot reviewed Aug 11, 2026

View reviewed changes

valentinpalkovic merged commit 9d54543 into next Aug 11, 2026
143 of 144 checks passed

valentinpalkovic deleted the valentin/angular-component-meta branch August 11, 2026 14:30

github-actions Bot mentioned this pull request Aug 11, 2026

Release: Prerelease 10.6.0-alpha.6 #35830

Merged

2 tasks done

coderabbitai Bot mentioned this pull request Aug 13, 2026

Angular: Hide class internals from the props table by default #35887

Merged

4 of 9 tasks

github-actions Bot mentioned this pull request Aug 17, 2026

Release: Prerelease 10.6.0-alpha.6 #35914

Closed

3 tasks

coderabbitai Bot mentioned this pull request Aug 20, 2026

Core: Make TypeScript's JSDoc semantics canonical for component docgen #35976

Merged

1 of 9 tasks

JReinhold added qa:skip Pull Requests that do not need any QA. (e.g. documentation) and removed qa:needed Pull Requests that will need manual QA prior to release. labels Aug 28, 2026

This was referenced Sep 5, 2026

chore(deps): bump @storybook/react-vite from 10.5.10 to 10.6.0 brandhaug/b2b-saas-starter#261

Merged

chore(deps): bump storybook from 10.5.10 to 10.6.0 brandhaug/b2b-saas-starter#263

Merged

Navigation Menu

Repository navigation

Angular: Add an in-process docgen analyzer, replacing Compodoc under the flag - #35805

Angular: Add an in-process docgen analyzer, replacing Compodoc under the flag#35805
valentinpalkovic merged 90 commits into
nextfrom
valentin/angular-component-meta

valentinpalkovic commented Aug 7, 2026 •

edited

Loading

Uh oh!

storybook-app-bot Bot commented Aug 7, 2026 •

edited

Loading

Uh oh!

valentinpalkovic commented Aug 7, 2026

Uh oh!

valentinpalkovic commented Aug 7, 2026

Uh oh!

coderabbitai Bot commented Aug 7, 2026 •

edited

Loading

Uh oh!

valentinpalkovic commented Aug 7, 2026

Uh oh!

coderabbitai Bot commented Aug 7, 2026 •

edited

Loading

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

huang-julien left a comment

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

valentinpalkovic commented Aug 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What I did

What it produces

Performance

Checklist for Contributors

Testing

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

Manual testing

Documentation

Checklist for Maintainers

Uh oh!

storybook-app-bot Bot commented Aug 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Package Benchmarks

@storybook/angular-vite

Uh oh!

valentinpalkovic commented Aug 7, 2026

Uh oh!

valentinpalkovic commented Aug 7, 2026

Uh oh!

coderabbitai Bot commented Aug 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

valentinpalkovic commented Aug 7, 2026

Uh oh!

coderabbitai Bot commented Aug 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

huang-julien left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

valentinpalkovic commented Aug 7, 2026 •

edited

Loading

storybook-app-bot Bot commented Aug 7, 2026 •

edited

Loading

`@storybook/angular-vite`

coderabbitai Bot commented Aug 7, 2026 •

edited

Loading

coderabbitai Bot commented Aug 7, 2026 •

edited

Loading