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.
Support yarn when installing deps for cap add
See original GitHub issueIf there is a yarn.lock in the root directory of a capacitor project, running cap add [platform] should install deps with yarn instead of npm. For projects using yarn, adding a platform takes way more time then it should, an a package-lock.json is generated unnecessarily. I could make a PR if requested.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:15 (13 by maintainers)
Top Results From Across the Web
yarn install
If yarn.lock is absent, or is not enough to satisfy all the dependencies listed in package.json (for example, if you manually add a ......
Read more >Install Yarn Ubuntu - Javatpoint
Yarn installs all packages in parallel but npm Installs a single package at a time. · Resolution- Yarn begins resolving dependencies by creating...
Read more >npm-install - npm Docs
This command installs a package and any packages that it depends on. If the package has a package-lock, or an npm shrinkwrap file,...
Read more >Setting up a project | Ethereum development ... - Hardhat
To initialize a Node.js project you can use npm or yarn . ... will create some directories and files and install the necessary...
Read more >How to use local Node packages as project dependencies
You can push your updates to a remote, and add that version as a dependency. For example with a Github repo you can...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Latest commit checks
capacitor.config.jsonfornpmClient, as well as prompting user during create (only if yarn is installed) and checking for--npm-client(as well asyarn.lock).The issue with
$npm_execpathis that I often use yarn to run commands in projects using npm, as therunkeyword is unnecessary as well as the--. Therefore, I think that$npm_execpathshould be ignored. Other than that, I agree with that order. What are your thoughts?