nuxt / nuxt/content

Comark support

Open
#3,844 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
3.7k
Forks
746
Avg merge
1d 16h
Merged PRs (30d)
3

Description

Is your feature request related to a problem? Please describe

@nuxtjs/mdc is being deprecated in favor of Comark.
https://github.com/nuxt-content/mdc#nuxt-mdc

Describe the solution you'd like

Comark support

Describe alternatives you've considered

Current workaround is to use @nuxt/content on dev, wile using comark on production.
This requires custom vite plugin.

Additional context

None.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the repository's existing @nuxtjs/mdc integration and the Comark documentation linked in the issue. No files or tests are named, so first identify the content-processing entry points and how the current custom Vite plugin workaround fits in. Done should mean Nuxt Content supports Comark without that production-only workaround, with coverage for the supported content path.

Written by the indexing model from the issue text.

Assessment

Tech stack
nuxtjs, typescript
Domain
content
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.