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

Cannot read property 'algolia' of undefined #228

Closed
herrbischoff opened this issue Apr 23, 2018 · 3 comments
Closed

Cannot read property 'algolia' of undefined #228

herrbischoff opened this issue Apr 23, 2018 · 3 comments

Comments

@herrbischoff
Copy link

Environment

$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.13.4
BuildVersion:	17E199
$ node -v
v8.10.0
$ vuepress -V
0.8.0

Issue

Just installed with yarn global add vuepress and followed the Getting Started instructions. When running vuepress dev or vuepress build the following error is thrown:

Extracting site metadata...TypeError: Cannot read property 'algolia' of undefined
    at resolveOptions (/Users/mbischoff/.config/yarn/global/node_modules/vuepress/lib/prepare.js:124:28)
    at prepare (/Users/mbischoff/.config/yarn/global/node_modules/vuepress/lib/prepare.js:24:25)
    at dev (/Users/mbischoff/.config/yarn/global/node_modules/vuepress/lib/dev.js:21:25)
    at args (/Users/mbischoff/.config/yarn/global/node_modules/vuepress/bin/vuepress.js:104:12)
    at Command.program.command.description.option.option.action (/Users/mbischoff/.config/yarn/global/node_modules/vuepress/bin/vuepress.js:31:21)
    at Command.listener (/Users/mbischoff/.config/yarn/global/node_modules/commander/index.js:315:8)
    at emitTwo (events.js:126:13)
    at Command.emit (events.js:214:7)
    at Command.parseArgs (/Users/mbischoff/.config/yarn/global/node_modules/commander/index.js:651:12)
    at Command.parse (/Users/mbischoff/.config/yarn/global/node_modules/commander/index.js:474:21)
@edm00se
Copy link
Contributor

edm00se commented Apr 23, 2018

I got the same, Windows 10, both PowerShell and from WSL (Ubuntu Bash). Rolling back to version 0.7.1 instead of the freshly released 0.8.0 works for me.

@yyx990803
Copy link
Member

Fixed in 0.8.1

@herrbischoff
Copy link
Author

Wow, that was quick! :) I can confirm this is now working for me. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants