-
Notifications
You must be signed in to change notification settings - Fork 51
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
[vue-loader] vue-template-compiler must be installed as a peer dependency, or a compatible compiler implementation must be passed via options. #3
Comments
Thanks for figuring this out. I'll be taking a look at it on the weekend. |
I pulled a new clone and built without issue. I believe the problem here was that you likely used Would you be so helpful and try out these steps? Thanks. |
Have just recently switched from npm to https://verdaccio.org/ Installed yarn. Don't like using brew on a mac and sure enough it gave me all kinds of warnings and required me to re-install node. Saved all that output and need to crawl over it to maybe spot a helpful message. Eventually I think I am ok...
Fail to run. Then I notice you said "yarn dev". That gets me further. Now it looks like it did last week. I have the electron app running and can navigate the file system. But it is has problems. Both npm and yarn say:
... but yarn installs it okay. The runtime error is:
The console messages are many (attached). node-gyp is some kind of problem child. So I don't know. Have I got something messed up in yarn/brew/node/npm/verdaccio ? I attach a log of what I did with screen prints. This may not be a big deal, my experience with these package tools is very very limited, and I'm no expert in vue, quasar and electron. Nor are my problems yours to resolve. I leave you with the log and screen prints, I won't know more until my guru returns late this week, or I make time to investigate further. Today time is limited. Thank you for the update. cmdline... ps: Last run shown in log is "quasar dev", but console prints from "yarn dev". |
Yeah, that's ugly. |
try these steps:
|
I merged in #1 which should fix this issue. Can you test, and if it works close this issue. If it doesn't work out for you, let me know. |
Module build failed (from ./node_modules/vue-loader/lib/index.js): I killed over an hour, reinstalling node and yarn and various. I gave it to my vue developer. Fresh machine. He also failed. Aggravating. No idea, sorry. I saved a text file of everything I ran if you want to see it. Pretty sure I have valid installs for yarn, node and npm now. I didn't quite understand changing the code change for "Any drawback to adding that so that it works with NPM?", did it anyway, no joy. Sorry I can't be more helpful. This is a disappointment for me and a constant worry now for dependency hell. I don't want to waste your time if this is my machine/config. Close the issue if you can't deal with it. I won't ask for more of your time. |
This package has been updated to use Quasar v1.14.1and Electron 10. The issue is no longer relevant. |
Vigorous hand clapping and thumbs up on your tutorial. You are a talented writer.
Thank you for sharing your work.
Build error:
Possible solutions:
https://myquickfix.co.uk/2019/01/08/fixing-vue-loader-vue-template-compiler-must-be-installed-as-a-peer-dependency/
https://medium.com/@nchutchind/i-ended-up-getting-the-following-error-vue-loader-vue-template-compiler-must-be-installed-as-a-37e8c007c1cc
But in my case...
I suppose this is related to the latest release of quasar. I see another having the same issue...
(https://forum.quasar-framework.org/topic/3110/fresh-install-of-quasar-cli-and-quasar-dev-won-t-work/4)
My webpack fu is not good enough to truly understand what is required of me here.
Later:
npm install --dev vue-template-compiler
That got me past this error. There are more issues but they were self-explanatory. The final build has "critical" errors but ran and behaved.
The text was updated successfully, but these errors were encountered: