Launching Vuepress Dev from newly install Vuepress cause > embedded between characters on README.md File.
Example:
echo '# Hello VuePress' > README.md
What is shown on webpage:
��#� �H�e�l�l�o� �V�u�e�P�r�e�s�s�
Vuepress: cli.js/1.0.0-alpha.36 win32-x64 node-v9.11.1
Also tried 0.14.8
Yarn: 1.10.1
Follow new install steps on website:
yarn global add vuepress
echo '# Hello VuePress' > README.md
vuepress dev
No � characters between letters.
��#� �H�e�l�l�o� �V�u�e�P�r�e�s�s� Being rendered instead of markdown header.
Inside webpack JS script on build looks like this:
(window.webpackJsonp=window.webpackJsonp||[]).push([[3],{168:function(t,e,n){"use strict";n.r(e);var s=n(0),i=Object(s.a)({},function(){this.$createElement;this._self._c;return this._m(0)},[function(){var t=this.$createElement,e=this._self._c||t;return e("div",{staticClass:"content"},[e("p",[this._v("��#� �H�e�l�l�o� �V�u�e�P�r�e�s�s�")])])}],!1,null,null,null);e.default=i.exports}}]);
Exampel Render Below:

Don't create the markdown file from CMD or PowerShell as it causes this issue, on windows create the file externally using windows explorer or code editor.
Yes, I'm also getting the same issue on both Vuepress 1.0.0-alpha.36 and latest stable 0.14.8.
My Vuepress is also installed as a global via yarn as instructed in the docs.
I think it may have something to do with the Windows version of echo and the type of file it creates. I created a clean file inside Sublime text and it doesn't appear to show these issues, but haven't had time to test fully. Will try again later.
Hi @SimonEast you are correct the echo on windows is causing rouge character between the creation of the MD file. I have created it from using VS code create the file and it works as intended might need to update docs to suggest not echo for windows.
See: https://github.com/vuejs/vuepress/issues/276#issuecomment-384930661
Most helpful comment
I think it may have something to do with the Windows version of
echoand the type of file it creates. I created a clean file inside Sublime text and it doesn't appear to show these issues, but haven't had time to test fully. Will try again later.