Vue docs update #661
Merged
Vue docs update #661
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
gauravtiwari
added a commit
that referenced
this pull request
Aug 22, 2017
* master: Update configuration.rb (#683) Check for config file before attempting to read (#664) Add back Https (#665) List possible causes of not finding a file in the manifest. (#676) Add missing space (#675) Fix output path Do not force SASS indented syntax in sass-loader (#672) Grammatical corrections in README Use hash for css as well Allow to use environments not present by default (#652) vue docs update (#661) Use hashed assets for all env (#653) Fix dev_server HMR reference and refresh after compile (#655)
gauravtiwari
pushed a commit
that referenced
this pull request
Aug 22, 2017
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.
I struggled to get this working, since the docs were slightly misleading for a Vue-n00b.
Thanks to @alevans4 for pointing me in the right direction!