question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Yorkie installation fails which causes Vue CLI to fail

See original GitHub issue

Version

3.2.1

Environment info

Environment Info:

  System:
    OS: Linux 4.9 Debian GNU/Linux 9 (stretch) 9 (stretch)
    CPU: (4) x64 Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz
  Binaries:
    Node: 11.3.0 - /usr/local/bin/node
    Yarn: 1.12.3 - /usr/local/bin/yarn
    npm: 6.4.1 - /usr/local/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmGlobalPackages:
    @vue/cli: 3.2.1

Steps to reproduce

vue create myapp

choose “default” setup

(Also tried the manual setup, which doesn’t work either…)

What is expected?

Vue installs successfully

What is actually happening?

yorkie@2.0.0 install /data/denni/Documents/git/cateroo-frontend/what/node_modules/yorkie node bin/install.js

fs.js:122 throw err; ^

Error: EINVAL: invalid argument, open ‘/data/denni/Documents/git/cateroo-frontend/what/node_modules/yorkie/package.json’

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! yorkie@2.0.0 install: node bin/install.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the yorkie@2.0.0 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Comments

I tried to install yorkie with npm install yorkie. That fails with the same error message, so it seems it is a problem with yorkie. Why is Vue depending on this? Yorkie doesn’t even have an issues tab on GitHub. Is Vue just using latest available version of dependencies? Seems like a great cause for failure.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:5
  • Comments:12

github_iconTop GitHub Comments

3reactions
Cebapecommented, Apr 2, 2020

This error (Yorkie@2.0.0) is related to the security attributes of the project-vuejs folder. So, create your projects outside the root / folder, make Linux updates (Ubuntu …) and success to everyone!

1reaction
stepansibcommented, Mar 13, 2019

Solved issue by using latest node image for container FROM node:latest

Read more comments on GitHub >

github_iconTop Results From Across the Web

Vue-cli 3: "command failed: npm install --loglevel error"
Try npm cache clean --force. If it doesn't work then manually delete %appdata%\npm-cache folder. Then try to create the project again.
Read more >
CLI Service - Vue CLI
If you overwrite the entry in the CLI, then the entries from config.pages are no longer considered, which may cause an error.
Read more >
From vue-cli to vitejs. I recently migrated some Vue2 projects…
I recently migrated some Vue2 projects from vue-cli / webpack to vitejs. After doing that for the third time, I started to have...
Read more >
@vue/cli-service | Yarn - Package Manager
Important: This documentation covers modern versions of Yarn. For 1.x docs, see classic.yarnpkg.com. Yarn.
Read more >
Build your first Vue 2 app today - CodingExercises.com
Installing the boilerplate Vue.js app with Vue CLI ... A common reason why this will fail is if we have apache running already, ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found