Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix incorrect TS types import path in documentation #2773

Merged
merged 1 commit into from
Sep 10, 2024

Conversation

ViliusP
Copy link
Contributor

@ViliusP ViliusP commented Sep 9, 2024

πŸ”— Linked issue

#2349

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

Resolves #2349

Currently, to import the type, you need to specify '@nuxt/content', but the documentation states it should be '@nuxt/content/dist/runtime/types'.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

Copy link
Member

@farnabaz farnabaz left a comment

Choose a reason for hiding this comment

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

Thanks

@farnabaz farnabaz merged commit abc4dd0 into nuxt:main Sep 10, 2024
1 check passed
@ViliusP ViliusP deleted the fix/export_types_docs branch September 10, 2024 16:31
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.

Export ParsedContent types
2 participants