Closed julijane closed 6 years ago
It works when I use npm install
instead.
Thanks for reporting this @julijane. I'm guessing you might be on Linux, where the default max file watchers is usually set to 8192. Installing with Yarn might create more files than installing with NPM, pushing the project over that limit. If you are on Linux, you should be able to increase the limit with these instructions.
Let me know if that helps! π
Thank you, that fixes it indeed. The warnings about unmet dependencies persist, though. While apparently they are harmless, if one does not know they are quite unsettling (but might not be your fault, I don't understand that enough, yet).
I agree the warnings are annoying. π That's a problem on Yarn's end that was fortunately fixed in version 1.4, so if you upgrade Yarn and try installing again, you shouldn't see them anymore. Let me know if that works for you. π
well...
$ yarn -v
1.6.0
Sorry, I was thinking of this similar issue. π You're absolutely right and I just opened an issue in Vue CLI proposing a potential fix for those warnings.
In case you're curious, Yarn (unlike NPM) doesn't recognize hoisted sub-dependencies as peer dependencies - so even though everything works, it still complains when no matching top-level dependency is found. Since this isn't something I can fix from here though, I'll close the issue.
Thanks for your patience. π
Understood. So thanks for your help so far. May I suggest that a hint regarding the file limitation on Linux is added to the documentation? While this is nothing specific of this package, I guess a one-liner should do and won't harm?
Great idea. π Just added that note.
I just cloned the latest and could not run node _start.js yarn install -- worked
yarn dev --open -- did not work first time I then tried npm run dev ---this worked I went back in retried yarn dev --open and it worked only after npm run dev
odd
Sorry if this is a simple problem, i'm not used to node. I did what the documentation said and this happened: