Vuepress: VuePress dev server not working

Created on 20 Apr 2018  路  17Comments  路  Source: vuejs/vuepress

  $ vuepress dev
  Extracting site metadata...[21:09:42] Compiling Client
  [21:09:46] Compiled Client in 4s

  VuePress dev server listening at http://localhost:8080/

On the road he does not show me anything as if I did not find him

Most helpful comment

Seeing spaces within @luisDanielRoviraContreras's project path, I assume this is also due to https://github.com/webpack/webpack-dev-server/issues/1373 and https://github.com/webpack/webpack-dev-middleware/issues/296.

Currently, webpack-dev-middleware can't handle spaces within the fully resolved path anymore.

I have also reproduced this behaviour for vuepress on my local Windows machine. Switching from C:\Users\Sebastian Niemann\myVuepressProject to C:\myVuepressProject is a possible workaround until it is solved.

All 17 comments

I got a 404 page.

Please at least provide your OS, Node version, vuepress version etc. We can't do anything with reports like this.

  • window
  • node v8.4.0
  • vuepress v0.7.0
    It shows me that if I compile but when I go to the locarl server with the port it literally appears Not Found

Do you have at least a README.md?...
You should provide a reproduction when reporting bugs because I can't guess all the things you didn't mention.

ok , i found the problem that suffix 'md' is not lowercase

run the tutorial litarialmente equal

   # install globally
    yarn global add vuepress # OR npm install -g vuepress

   # create a markdown file
    echo '# Hello VuePress' > README.md

   # start writing
   vuepress dev

   # build 
   vuepress build

the name of readme is

README.md

Could they at least explain to me why the file does not work? It has to be readme.md? in lowercase everything? or I do not understand and of course when I say follow literal is to execute a command at a time not everything until comments

could give me a functional example please really I love the proposal of vuepress at the moment use hexo and I would love to migrate to vuepress

I hope this helps to better understand sorry for the inconvenience

Oh I thought @xubowenjx was the author of this issue.

Seeing spaces within @luisDanielRoviraContreras's project path, I assume this is also due to https://github.com/webpack/webpack-dev-server/issues/1373 and https://github.com/webpack/webpack-dev-middleware/issues/296.

Currently, webpack-dev-middleware can't handle spaces within the fully resolved path anymore.

I have also reproduced this behaviour for vuepress on my local Windows machine. Switching from C:\Users\Sebastian Niemann\myVuepressProject to C:\myVuepressProject is a possible workaround until it is solved.

@SebastianNiemann
Thank you very much but where does my route have spaces?

@luisDanielRoviraContreras
You have a space in your Windows-generated user path, because of the username "pc 01".

@Ragura @SebastianNiemann

Thanks alfin I worked with the name change without spaces :grinning: .

@SebastianNiemann thank you, you saved me from a night full of headaches!
I was trying to implement express and webpack with webpack-dev-middleware and it kept failing on me. the process wouldn't write files to a directory

The dev script said it was "listening at http://localhost:8080" but I had to access at http://0.0.0.0:8080

The dev script said it was "listening at http://localhost:8080" but I had to access at http://0.0.0.0:8080

The same issue happened to me. I did what @ajthenewguy did and now I can access the doc.

Thanks to Evan, I realised I had README.MD (the file extension was in caps), causing a 404 on the index page.

Should I create an issue for this?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

lesliecdubs picture lesliecdubs  路  3Comments

herrbischoff picture herrbischoff  路  3Comments

higuoxing picture higuoxing  路  3Comments

gaomd picture gaomd  路  3Comments

AMontagu picture AMontagu  路  3Comments