Skip to content

feat(nuxt): add option to disable module - #231

Open
hacknug wants to merge 2 commits into
romhml:mainfrom
hacknug:feat/enabled-setting
Open

hacknug wants to merge 2 commits into
romhml:mainfrom
hacknug:feat/enabled-setting

Conversation

@hacknug

@hacknug hacknug commented Nov 10, 2026

Copy link
Copy Markdown

This PR adds an option to disable the module without the need to remove it from the modules array.

Copilot AI balanced review requested due to automatic review settings November 10, 2026 12:15

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The disabled path lacks regression coverage verifying that the app still renders with the module registered and enabled: false, while the Compodium renderer and API remain uninstalled.

1 open issue
What changed in this PR

Adds an opt-out for the Nuxt integration so applications can disable Compodium without removing it from the modules array.

Changes:

  • Adds a documented enabled option that defaults to true.
  • Returns early from module setup when disabled, preserving existing behavior by default.
File Description
packages/​nuxt/​src/​module.ts Defines the enabled option, its default, and the setup guard.

Review effort: Balanced

Comment thread packages/nuxt/src/module.ts Resolved

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants