What is the equivalent of “npm install –save” in Yarn?
The yarn equivalent tonpm install <name> –save is: yarn add <name> Here’s the link to the docs for the full list of commands in comparison to npm.
yarnpkg
npm equivalent of yarn resolutions?
Npm equivalent to yarn resolutions is overrides. After the RFC was accepted now there’s an epic to watch the progress of implementation. https://github.com/npm/statusboard/issues/343 Edit: This was released in npm v8.3.0 Documentation: https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides To make sure the package foo is always installed as version 1.0.0 no matter what version your dependencies rely on: { “overrides”: { … Read more
Run yarn in a different path
You can use –cwd like so yarn –cwd <path> <yarn command>. The order of arguments is important. Example: yarn –cwd ~/test_project/ dev Because the following will not work: yarn dev –cwd ~/test_project/
How do you resolve Git conflicts in yarn.lock
Since Yarn 1.0 it’s easy because it has built in support for this scenario. First solve the conflict in package.json manually, then just run this: $ yarn install yarn install v1.0.1 info Merge conflict detected in yarn.lock and successfully merged. [1/4] Resolving packages… And then the conflict will be resolved and you can commit that … Read more
Yarn – There appears to be trouble with your network connection. Retrying
This happens when your network is too slow or the package being installed is too large, and Yarn just assumes it’s a network problem. Try increasing Yarn network timeout: yarn add <yourPackage> –network-timeout 100000
‘TypeError [ERR_INVALID_ARG_TYPE]: The “path” argument must be of type string. Received type undefined’
To fix this issue simply upgrade react-scripts package (check latest version with npm info react-scripts version): Replace in your package.json “react-scripts”: “^3.x.x” with “react-scripts”: “^3.4.1” (or the latest available version) (optional for some) Delete your node_modules folder Run npm install or yarn install Some people reported that this issue was caused by running npm audit … Read more
error: no template named ‘remove_cv_t’ in namespace ‘std’; did you mean ‘remove_cv’?
Update: Since node-sass version 6.0.1, Node 16 is supported. Updating node-sass to a version higher than 6.0.1 solves this issue. What you’re seeing is an error during compilation of node-sass. That’s a package processing your Sass/SCSS styles, which is written in C++ and only re-packaged as a JavaScript library. The fact it’s written in C++ … Read more
How to install package with local path by Yarn? It couldn’t find package
For yarn version < 2.x Yarn requires prefix file: for local packages. For relative path: yarn add file:./../your-project For absolute path yarn add file:/dev/your-project For your example, dependency in package.json would be declared as follows: “my-custom-i18n”: “file:./../MyProject.Shared/myproject-i18n”, This works both for Yarn and NPM as well. It is incompatibility with NPM client, Yarn team is … Read more
Module not found: Error: Can’t resolve ‘core-js/es6’
The imports have changed for core-js version 3.0.1 – for example import ‘core-js/es6/array’; and import ‘core-js/es7/array’; can now be provided simply by the following import ‘core-js/es/array’; if you would prefer not to bring in the whole of core-js
Should I commit yarn.lock and package-lock.json files?
Always commit dependency lock files in general As is covered elsewhere, dependency lock files, which are supported by many package management systems (e.g.: composer and bundler), should be committed to the codebase in end-of-chain projects – so that each individual trying to run that project is doing so with exactly the tested set of dependencies. … Read more