apps/docs/src/docs.md (1)

195-207: Incorrect import for unplugin-vue-components (Vite).

The example imports a named export from the package root, which will break. For Vite, import the default from 'unplugin-vue-components/vite' (as shown earlier in this page).

-```ts
-import {Components} from 'unplugin-vue-components'
+```ts
+import Components from 'unplugin-vue-components/vite'
 import {BootstrapVueNextResolver} from 'bootstrap-vue-next/resolvers'
 
 Components({
   resolvers: [
     BootstrapVueNextResolver({
       aliases: {
         BInput: 'BFormInput',
       },
     }),
   ],
 })

</blockquote></details>

</blockquote></details>

♻️ Duplicate comments (1)

apps/docs/src/docs/components/app.md (1)

354-366: Confirm removals and tighten the migration wording; add an explicit “how to replace” note.

Two asks:

• Please verify the exact removal version and plugin list (modalControllerPlugin, toastControllerPlugin, popoverControllerPlugin) and that orchestratorPlugin is the intended replacement in all cases.
• Minor grammar/flow tweak and an explicit action sentence will reduce confusion.

Apply this doc-only diff to streamline the admonition and clarify the action:

-::: warning Migration Note
-
-Plugins will show deprecation warnings but continue to work until removed in a future version, with
-the following exceptions:
-
-- `modalControllerPlugin`
-- `toastControllerPlugin`
-- `popoverControllerPlugin`
-
-These plugins have been removed as of **version 0.40.0**.
-Please replace references to these with a reference to `orchestratorPlugin`.
-
-:::
+::: warning Migration note
+The following controller plugins were removed in **v0.40.0**:
+
+- `modalControllerPlugin`
+- `toastControllerPlugin`
+- `popoverControllerPlugin`
+
+Replace any usage with `orchestratorPlugin`.
+
+All other legacy plugins will continue to emit deprecation warnings until they are removed in a future version.
+:::

Optionally, add a one-line pointer after the admonition to the legacy-plugin example in this page or to the migration guide.

I can scan the codebase and surface any remaining references to the removed plugins (docs and code) and propose a follow-up PR that replaces or removes them.

🧹 Nitpick comments (3)

apps/docs/src/docs.md (3)

133-139: Good call-out for legacy controller plugins; consider titling the admonition.

Adding a short title improves scan-ability.

-::: warning
+::: warning Legacy controller plugins
@@
 :::

---

140-140: Grammar: “Automatic Registration of Components”

Use the noun “Registration” instead of the gerund “Registering”.

-### Automatic Registering of Components
+### Automatic Registration of Components

---

360-368: Solid guidance; consider softening the footprint number or linking to measurement.

“~20kb gzipped” can drift over time. Either say “roughly 20kb gzipped (subject to change)” or link to a perf/bundle report page in the docs.

If you’d like, I can add a tiny script that generates a fresh bundle size snapshot using vite-bundle-visualizer and a minimal sample app to keep this number honest in future releases.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 460030a and 7e6a1b4.

📒 Files selected for processing (2)

• apps/docs/src/docs.md (2 hunks)
• apps/docs/src/docs/components/app.md (2 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: xvaara
PR: bootstrap-vue-next/bootstrap-vue-next#2701
File: apps/docs/src/docs/migration-guide.md:622-626
Timestamp: 2025-06-05T11:43:10.793Z
Learning: In migration guides, links to the old/previous version's documentation (like bootstrap-vue.org) are appropriate and helpful when explaining deprecated features, as they provide users with reference points for what they're migrating from.

📚 Learning: 2025-08-19T14:23:46.746Z

Learnt from: xvaara
PR: bootstrap-vue-next/bootstrap-vue-next#2732
File: packages/bootstrap-vue-next/CHANGELOG.md:35-41
Timestamp: 2025-08-19T14:23:46.746Z
Learning: In the bootstrap-vue-next repository, CHANGELOG.md files (e.g., packages/bootstrap-vue-next/CHANGELOG.md) are autogenerated and should be ignored in reviews; do not propose edits for them.

Applied to files:

• apps/docs/src/docs.md

🪛 LanguageTool

apps/docs/src/docs.md

[grammar] ~135-~135: There might be a mistake here.
Context: ...llerPlugin, toastControllerPlugin, or popoverControllerPlugin`, please see th...

(QB_NEW_EN)

apps/docs/src/docs/components/app.md

[grammar] ~356-~356: There might be a mistake here.
Context: ... until removed in a future version, with the following exceptions: - `modalContr...

(QB_NEW_EN)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

🔇 Additional comments (2)

apps/docs/src/docs/components/app.md (2)

15-15: Nice: clear cross-reference to migration details.

Pointing readers to the Backward Compatibility section from the feature bullets improves discoverability.

---

354-366: Deprecation removals and replacement usage verified; no action required

The verification script confirms that:

• modalControllerPlugin, toastControllerPlugin, and popoverControllerPlugin only appear in the documentation (apps/docs/src/docs…) and are not exported or used in the codebase.
• orchestratorPlugin is defined and exported in packages/bootstrap-vue-next/src/plugins/orchestrator/index.ts and correctly consumed (e.g., in createBootstrap/index.ts).

No further changes are needed.