I'm currently working on a Nuxt 3 project and have encountered a concern regarding dependencies. It appears that @nuxt/content version 2.10.0 relies on shiki-es@0.14.0, which has been marked as deprecated.
Describe the bug
Issue Description:
While performing a dependency audit using pnpm why shiki-es, I discovered this deprecated dependency. Given the importance of maintaining up-to-date and secure dependencies, this raises concerns about future compatibility and potential security issues.
Expected Behavior:
Ideally, @nuxt/content should use up-to-date, actively maintained dependencies to ensure the stability and security of projects that depend on it.
Steps to Reproduce:
In a Nuxt 3 project, add @nuxt/content version 2.10.0.
Run pnpm why shiki-es to see the dependency chain.
Is there a plan to update or replace this deprecated subdependency in an upcoming release of @nuxt/content? Any information or guidance on this would be greatly appreciated.
Additional context
Thank you for your attention to this matter and your continued work on @nuxt/content.
Environment
Build Modules: -
Context
I'm currently working on a Nuxt 3 project and have encountered a concern regarding dependencies. It appears that
@nuxt/content
version 2.10.0 relies onshiki-es@0.14.0
, which has been marked as deprecated.Describe the bug
Issue Description: While performing a dependency audit using
pnpm why shiki-es
, I discovered this deprecated dependency. Given the importance of maintaining up-to-date and secure dependencies, this raises concerns about future compatibility and potential security issues.Expected Behavior: Ideally,
@nuxt/content
should use up-to-date, actively maintained dependencies to ensure the stability and security of projects that depend on it.Steps to Reproduce:
@nuxt/content
version 2.10.0.pnpm why shiki-es
to see the dependency chain.Is there a plan to update or replace this deprecated subdependency in an upcoming release of
@nuxt/content
? Any information or guidance on this would be greatly appreciated.Additional context
Thank you for your attention to this matter and your continued work on
@nuxt/content
.Logs