docs: distinguish telemetry config between Nuxt 3 and Nuxt 4 #298
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
β Type of change
π Description
This PR updates the README.md documentation to clearly distinguish between Nuxt 3 and Nuxt 4 telemetry configuration syntax.
Changes made:
telemetry: false/telemetry: truetelemetry: { enabled: false }/telemetry: { enabled: true }Why this change is required:
Nuxt 4 introduced a new telemetry configuration format using an object with an
enabledproperty, while Nuxt 3 used a simple boolean. This change helps users understand the correct syntax for their specific Nuxt version and prevents configuration errors.Problem solved:
Users were previously confused about the correct telemetry configuration syntax, especially when migrating from Nuxt 3 to Nuxt 4 or when following documentation examples that didn't specify the version.