I realized that the dist was not automatically building on push to master, and upon further investigation it turns out I needed to release. It's my first time doing so, so I might be handling it incorrectly.

Steps to reproduce:

• go to the sidebar in my repository titled "Releases"
• choose a tag (I chose v0.1.2)
• publish

Errors:
Upon looking at my workflow, it seems dist is not created because it fails at the below:

Run rm -rf .ci_badges
npm WARN exec The following package was not found and will be installed: [email protected]


✔️   msoup-blog v3.1.9: Badges updated successfully!
    
    # version 3.1.9
    # dependencies 8
    # devDependencies 8


HEAD detached at v0.1.2
nothing to commit, working tree clean
Error: Process completed with exit code 1.

Would someone be able to provide any hints?

I have a feeling that HEAD detached at v0.1.2 is probably a big hint, but I'm unsure why this is happening.

Hi there, it looks like the template says that syntax highlighting is supported, but I'm not finding a way to implement it.

The markdown-it documentation suggests that we need to wrap our markdown with
'highlight.js'.

I found this solution which involves adding rules to nuxt.config, but this project doesn't seem to use nuxt.

The markdown-it documentation also provides this example

var hljs = require('highlight.js'); // https://highlightjs.org

// Actual default values
var md = require('markdown-it')({
  highlight: function (str, lang) {
    if (lang && hljs.getLanguage(lang)) {
      try {
        return hljs.highlight(str, { language: lang }).value;
      } catch (__) {}
    }

    return ''; // use external default escaping
  }
});

However, the way that the template imports the markdown looks like this

const markDownIt = new MarkdownIt({ html: true }).use(emoji)

const postHtml = markDownIt.render(markDownSource)

How would I wrap the postHtml with the highlighter and subsequently apply the github hightlighting rules to it?

Hi, is it possible to specify custom vue components in the markdown file that will be rendered afterwards? e.g. <my-button>Hi</my-button> will then become <a class="btn">Hi</a> as html element