Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

windows user issue collection (VuePress 1.x Alpha) #913

Closed
ulivz opened this issue Oct 7, 2018 · 14 comments
Closed

windows user issue collection (VuePress 1.x Alpha) #913

ulivz opened this issue Oct 7, 2018 · 14 comments
Labels
type: question or discussion Question or discussion

Comments

@ulivz
Copy link
Member

ulivz commented Oct 7, 2018

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:

/cc @mAKEkr @ekoeryanto

@ulivz ulivz added the type: question or discussion Question or discussion label Oct 7, 2018
@ulivz
Copy link
Member Author

ulivz commented Oct 7, 2018

About this issue:

image

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 [email protected], @mAKEkr @ekoeryanto could you help check if the new version fix it?

@meteorlxy
Copy link
Member

@ulivz Still error for me.

@ulivz
Copy link
Member Author

ulivz commented Oct 7, 2018

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

@meteorlxy
Copy link
Member

meteorlxy commented Oct 7, 2018

@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
Copy link
Member Author

ulivz commented Oct 7, 2018

@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 [email protected], could you confirm again? Thanks.

@mAKEkr
Copy link
Contributor

mAKEkr commented Oct 7, 2018

now i install [email protected], running complete without error. thanks @ulivz :)

@vuejs vuejs deleted a comment from ekoeryanto Oct 10, 2018
@vuejs vuejs deleted a comment from ekoeryanto Oct 10, 2018
@chenweigao
Copy link

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
Copy link
Contributor

mAKEkr commented Oct 12, 2018

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

@chenweigao
Copy link

chenweigao commented Oct 13, 2018

@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
Copy link
Contributor

mAKEkr commented Oct 13, 2018

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

@ulivz
Copy link
Member Author

ulivz commented Oct 21, 2018

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

@chenweigao
Copy link

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

@ltstriker
Copy link

ltstriker commented Dec 14, 2018

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
Copy link
Member

Close as it's stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question or discussion Question or discussion
Projects
None yet
Development

No branches or pull requests

5 participants