Vue mode exposes build environment file path

[metzg]

hi,

Thank you for the useful plugin.

When using Vue, the hmrId property in the compiled code is still present when building for production, and contains the full path of the source markdown file, adding extra bytes of payload and possibly exposing internal information.

Relevant line in the source code:

vite-plugin-markdown/src/index.ts

Line 156 in 1c1dfb4

content.addContext(compiledVueCode.replace('\nexport function render(', '\nfunction vueRender(') + `\nconst VueComponent = { render: vueRender }\nVueComponent.__hmrId = ${JSON.stringify(id)}\nconst VueComponentWith = (components) => ({ components, render: vueRender })\n`)

Production build result (line breaks added for readability):

import{o as i,c as n,F as a,a as e}from"./index-C12kFbxv.js";const m={title:"Hello world"},l=e("h1",null,"Hello world",-1),r=e("p",null,"Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.",-1),u=e("p",null,[e("img",{src:"favicon.ico",alt:"hi"})],-1);function o(t,s){return i(),n(a,null,[l,r,u],64)}const c={render:o};
c.__hmrId="/home/will/playground/md-test/src/content/blog/hello.md";
const p=t=>({components:t,render:o});export{c as VueComponent,p as VueComponentWith,m as attributes};

If I understand this right, the hmr id could be removed when there is no hmr by checking for import.meta.hot.