windows user issue collection (VuePress 1.x Alpha)

[ulivz]

This issue was for windows users who are using VuePress 1.x Alpha. since I don't use win and even don't have one, so specially create this issue, concentrate all the issues, and hope to solve it with the help of everyone.

For now the urgent issues was path handling at windows:

• Installation instructions on VuePress home page don't work #908
• Blog plugin: category, tag page don't work #881 (comment)
• fix: webpack absolute output path #886

/cc @mAKEkr @ekoeryanto

[ulivz]

About this issue:

After some investigation, I find that we don't need to sunset upath, it's mainly caused by this compressed style which would take unexpected result at windows:

path.resolve(outDir)

I try to fix it at f62cd73 and publish it at vuepress@1.0.0-alpha.5, @mAKEkr @ekoeryanto could you help check if the new version fix it?

[meteorlxy]

@ulivz Still error for me.

[ulivz]

@meteorlxy What's the detailed error log? Don't paste image, thanks.

[meteorlxy]

@ulivz

Same error as you posted above.

(sorry I just tried and left my lab, so couldn't paste at this moment 😅)

---- update error log here
dev command error:

WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.output.path: The provided value "C:/Users/meteo/Desktop/projects/meteorlxy/test/.vuepress/dist" is not an absolute path!
   -> The output directory as **absolute path** (required).
    at webpack (C:\Users\meteo\Desktop\projects\meteorlxy\test\node_modules\webpack\lib\webpack.js:31:9)
    at dev (C:\Users\meteo\Desktop\projects\meteorlxy\test\node_modules\@vuepress\core\lib\dev.js:95:20)
    at process._tickCallback (internal/process/next_tick.js:68:7)

build command error:

WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration[0].output.path: The provided value "C:/Users/meteo/Desktop/projects/meteorlxy/test/.vuepress/dist" is not an absolute path!
   -> The output directory as **absolute path** (required).
 - configuration[1].output.path: The provided value "C:/Users/meteo/Desktop/projects/meteorlxy/test/.vuepress/dist" is not an absolute path!
   -> The output directory as **absolute path** (required).
    at webpack (C:\Users\meteo\Desktop\projects\meteorlxy\test\node_modules\webpack\lib\webpack.js:31:9)
    at Promise (C:\Users\meteo\Desktop\projects\meteorlxy\test\node_modules\@vuepress\core\lib\build.js:93:7)
    at new Promise (<anonymous>)
    at compile (C:\Users\meteo\Desktop\projects\meteorlxy\test\node_modules\@vuepress\core\lib\build.js:92:12)
    at build (C:\Users\meteo\Desktop\projects\meteorlxy\test\node_modules\@vuepress\core\lib\build.js:42:23)

[ulivz]

@meteorlxy Cool, your log is so clear, and I can basically confirm that this is an edge case issue of webpack. (webpack/webpack#66),

Fixed at d89f766 and released at vuepress@1.0.0-alpha.6, could you confirm again? Thanks.

[mAKEkr]

now i install vuepress@1.0.0-alpha.8, running complete without error. thanks @ulivz :)

[chenweigao]

there is a problem in config the plugin 'last-updated' :

 WARN  [@vuepress/last-updated] Invalid value for "pluginOptions" @vuepress/plugin-last-updated: expected a Object or Boolean but got String.

and in the 1.x version, I have used

 plugins: {
    '@vuepress/last-updated': true
  },

but failed to show the message, I am the newer of this, so if this a change or a bug... :

[mAKEkr]

@chenweigao can you had try an clean installation using an yarn? this issue don't reproduce on my environment.

[chenweigao]

@mAKEkr I use both yarn and npm in my project, and when I build it I use npm run, when I install the dependence, I use the yarn add ... is that causes a problem? I cannot understand what ‘an clean installation’ means?could you please give me a direction?

[mAKEkr]

@chenweigao I mean remove all file in node_modules directory, and try running install. my environment somtimes npm crashed installation without error message.

[ulivz]

@chenweigao This issue of last-update has been fixed at b8ce22c. and you can install the latest alpha version to check it.

[chenweigao]

@ulivz thank you very much. it is a good job!
best wishes

[ltstriker]

the base seems must be that, or the js file cannot be found?

Are you sure? Hmmm... don't know what to say.

Yes.I use the default base at first.But it will find the js file in the path E:/assets/.....
It is a wrong path,so that it make load fail.(It seems a bug too, I think)
I just try to change the base to (/retryvpress/docs/.vuepress/dist/) to fix it to find in the path E://retryvpress/docs/.vuepress/dist/assets/.......
Then the js files were found but just jump 404 soon.
Is it lead to the 404?
@ulivz

---

Both dev and build succeed,no error log.

[meteorlxy]

Close as it's stale