marp-team/marp-vue is a UI-focused project on GitHub with 25 stars, written primarily in TypeScript. [INACTIVE] Marp renderer component for Vue
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
This component is suited to create presentation tools integrated with Marp by Vue. Marp would create the static slide contents consist of plain HTML and CSS, so you have to notice that it's not suited to control the content of your slide by Vue.
Eagle.js framework is a good choice to create beautiful slide contents with making full use of Vue power. If you really think to need, you can even use Marp Vue in that frameworks.
We also provide Marp component and actually MarpRenderer is an alias to Marp. We recommend to use MarpRenderer becasue the multi-word component name is an essential rule in Vue style guide.
Constructor option
Marp constructor options can change in options prop.
:information_source: See also Scoped Slots in the document of Vue.
MarpWorker component (Experimental)
For the best performance of the integrated web app, MarpWorker component allows using Web Worker for Markdown conversion. It has a lot of clear advantages over a regular MarpRenderer component.
It does not block UI thread while converting large Markdown.
A blazing fast live preview by a simple but clever queueing system is available.
No longer need to include a huge Marp Core into main JS.
Web Worker will be loaded asynchronously, so the first paint will not block.
The renderer using worker may be default component of Marp Vue in future.
Basic usage
You can use it just by swapping from MarpRenderer to MarpWorker. By default, MarpWorker will use a pre-built worker via jsDelivr CDN.
MarpWorker's custom renderer might be called with undefined slides argument, unlike Marp. It means an initial rendering of the component while preparing worker.
You may show waiting user a loading message as follows:
Yes — marp-team/marp-vue ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/marp-team/marp-vue.
What else is in the Frontend space?
marp-team/marp-vue is tracked by TopGit under the Frontend category, alongside 3 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What is marp-team/marp-vue?
marp-team/marp-vue (marp-team/marp-vue) is a TypeScript project on GitHub. From the project's own README: [INACTIVE] Marp renderer component for Vue
What license does marp-team/marp-vue use?
marp-team/marp-vue is released under the MIT license. Always verify the LICENSE file directly on GitHub for the authoritative terms — license strings can be edited out of sync with a project's actual stance.
Where can I see marp-team/marp-vue in action?
The project maintains a homepage at https://marp-vue.netlify.com/. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about marp-team/marp-vue?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/marp-team/marp-vue is the definitive source.
Why is marp-team/marp-vue categorized under Frontend?
TopGit places marp-team/marp-vue in the Frontend category based on its GitHub topics and description (tagged: "marp", "vue", "vue-components"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Still deciding about marp-vue?
One click hands the question to an AI along with this page — see what it says about marp-vue.