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

build will fail when .vuepress/component has script tag #502

Closed
genedronek opened this issue May 25, 2018 · 4 comments
Closed

build will fail when .vuepress/component has script tag #502

genedronek opened this issue May 25, 2018 · 4 comments

Comments

@genedronek
Copy link

Bug report

Version

most current vuepress 0.9.0

Steps to reproduce

git  from https://github.com/genedronek/vuepress-bug.git
cd vuepress-bug
vuepress build docs

What is expected?

"vuepress build docs" should work

What is actually happening?

build blows up; bad default object, and other manifestations

Other relevant information

any .vuepress/component with script will cause failure

  • Your OS: Mac Sierra
  • Node.js version: v10.2
  • Browser version: n.a.
  • Is this a global or local install?
    global, but either kind, local or global, vuepress build will fail.
  • Which package manager did you use for the install?
    npm install -g vuepress;

I performed complete reload of node and npm just to make sure this is current bug.

@chrtz
Copy link

chrtz commented May 25, 2018

That seems to be the same issue (#500) I have to face since today.

but I created a repo (https://github.com/chrtz/vuepress_repo) for showing the bug, and there it strangely doesn't occur.

@ulivz
Copy link
Member

ulivz commented May 27, 2018

Just tested with latest version and all works for me:

image

@ulivz
Copy link
Member

ulivz commented May 27, 2018

Closing it since we cannot reproduce it, please feel free to continue discussion. we'll reopen this issue if a proper repro is posted.

@ulivz ulivz closed this as completed May 27, 2018
@chrtz
Copy link

chrtz commented May 27, 2018

I think it could be possible this has to do with the new npm (6.10) and the audit function. As there are two vulnerabilities according to string.js.

(#493)

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