Dev #387
Closed
Dev #387
Conversation
This file contains hidden or 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
added 2 commits August 6, 2014 16:19
… template-parser.js.js
| Are you sure it's not your setup's problem? |
| Aha, I was using http://jspm.io to load Vue which fetches all the dependencies one by one but it seems like it does not resolve the deps the same way as Node. Appologies for raising a false flag! |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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 simply changed how some of the core modules were being incorrectly required in 'main.js' and 'utils.js'. That resulted in errors when requiring Vue in Node.js because those dependencies were not being resolved correctly. Please see the commit messages.