-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Variable parent
is undefined
#1098
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
``` ReferenceError: parent is not defined at VueComponent.render (node_modules/@vuepress/core/lib/app/components/Content.js:17:6) at VueComponent.Vue._render (/Users/prefer/src/kernelcare-doc/node_modules/vue/dist/vue.runtime.common.js:4642:22) at renderComponentInner (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:7518:25) at renderComponent (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:7488:5) at RenderContext.renderNode (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:7404:5) at RenderContext.next (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:2469:23) at cachedWrite (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:2323:9) at renderStringNode$1 (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:7599:5) at RenderContext.renderNode (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:7402:5) at RenderContext.next (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:2469:23) at cachedWrite (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:2323:9) at renderElement (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:7642:5) at renderNode (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:7406:5) at renderComponentInner (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:7524:3) at renderComponent (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:7488:5) at RenderContext.renderNode (/Users/prefer/src/kernelcare-doc/node_modules/vue-server-renderer/build.js:7404:5) ```
This issue is a blocker for running |
ulivz
approved these changes
Dec 13, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
kamontat
pushed a commit
to kcnt-deprecated/website
that referenced
this pull request
Dec 13, 2018
due to alpha version cause parent is undefined vuejs/vuepress#1098 This closes #63
kamontat
pushed a commit
to kcnt-deprecated/website
that referenced
this pull request
Dec 13, 2018
* feat(css): migrate with bulma * fix(doc-web): update to latest version to avoid error in vuepress due to alpha version cause parent is undefined vuejs/vuepress#1098 This closes #63 * ci(caches): increase caches to remove old version * perf(css): changes css module tailwindcss have a huge problem with scss & sass, and they also have a lot of problem with size so I discuss to use bulma instead with purgecss which tested on bulma css file this changes make our website size decrease from 2 MB to 200 KB This closes #62 BREAKING CHANGE: do not use tailwindcss and change to bulma instead
kamontat
pushed a commit
to kcnt-deprecated/website
that referenced
this pull request
Dec 18, 2018
* refactor(cms): remove test data in prang folder * feat(ui): implement design on main cms since website is hosting 2 portfolio so I have to separate cms into 2 main, so I create a my cms page that you can choose which cms you want to open This closes #52 * feat(icon): redesign application icon in varity format * refactor(icon): app icon seperate dash * perf(doc-web): improve search dialog, using algolia search This closes #58 * chore(deps): update dependency @vuepress/plugin-google-analytics to v1.0.0-alpha.29 (#61) * chore(deps): update semantic-release monorepo (#59) * chore(deps): update dependency @vuepress/plugin-back-to-top to v1.0.0-alpha.29 (#60) * Merge pull request #64 from kamontat/improve/style * feat(css): migrate with bulma * fix(doc-web): update to latest version to avoid error in vuepress due to alpha version cause parent is undefined vuejs/vuepress#1098 This closes #63 * ci(caches): increase caches to remove old version * perf(css): changes css module tailwindcss have a huge problem with scss & sass, and they also have a lot of problem with size so I discuss to use bulma instead with purgecss which tested on bulma css file this changes make our website size decrease from 2 MB to 200 KB This closes #62 BREAKING CHANGE: do not use tailwindcss and change to bulma instead * feat(content): update language of net * fix(css): i don't want to load bulma on every pages * fix(404): make custom 404 with netlify website * build(dep): remove unused libraries * refactor(deps): move renovate configuration out as sharable config repo * docs(readme): remove code quality badge because unsolvable issue Code quality badge always show as fail because unknown coverage result has updated to server * perf(helper): remove commit script, use committ instead * build(docs): remove document website out, to kcnt-info/documents * style(changelog): update markdown * chore(deps): update dependency enquirer to v2.2.0 (#68) * chore(deps): remove unused libs * docs(packagejson): name package name * chore(trigger): trigger ci to rebuild * ci(sonar): update sonar config * docs(sonar): update sonar badge
kamontat
pushed a commit
to kcnt-deprecated/website
that referenced
this pull request
Dec 18, 2018
# [1.1.0](v1.0.4...v1.1.0) (2018-12-18) * Merge pull request #69 from kcnt-info/dev ([d682ee2](d682ee2)), closes [#69](#69) [#52](#52) [#58](https://github.com/kcnt-info/website/issues/58) [#61](#61) [#59](#59) [#60](#60) [#64](#64) [vuejs/vuepress#1098](vuejs/vuepress#1098) [#63](#63) [#62](#62) [#68](#68) ### BREAKING CHANGES * do not use tailwindcss and change to bulma instead * feat(content): update language of net * fix(css): i don't want to load bulma on every pages * fix(404): make custom 404 with netlify website * build(dep): remove unused libraries * refactor(deps): move renovate configuration out as sharable config repo * docs(readme): remove code quality badge because unsolvable issue Code quality badge always show as fail because unknown coverage result has updated to server * perf(helper): remove commit script, use committ instead * build(docs): remove document website out, to kcnt-info/documents * style(changelog): update markdown
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
vuepress version - 1.0.0-alpha.28
When I try to run
yarn docs:build
I get the error:Summary
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx]
, where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information: