When I run yarn install (or just yarn for short) and I don't have a yarn.lock file yet, will the result depend on what packages are already installed in my node_modules directory? Or will node_modules end up in the same state regardless of what's already in there?
In other words, do I need to run rm -rf node_modules "just in case" before running yarn, to make sure that I get the latest versions?
yarn seems to wipe node_modules, generate a lockfile, then download everything without lockfile for me (0.18.1).
If I then modify node_modules, further yarn calls don't do anything, but adding a dependency introducing a change to the lockfile then calls it to wipe my node_modules again.
(I recall reading a yarn github thread about how wiping node_modules for any lockfile changes being the normal behavior, but now I don't know how to find that comment)
Related
After upgrading to yarn 3, when I run yarn install, the resolutions are getting removed from package.json and added in yarn.lock file.
Are resolutions not supposed to reside in package.json when using yarn 3?
You need to use yarn set resolution with the newer versions of yarn: https://yarnpkg.com/cli/set/resolution
Warning! To persist the changes, use the -s flag or you'll lose the custom resolution when you regenerate your yarn.lock file.
I'm a bit confused.
I accidentally installed yarn in a project. I just ran the command yarn that installed the yarn in the project. How do I uninstall yarn from the project?
Do I type in npm uninstall yarn? to uninstall it from a project?
I looked at other solutions and I'm confused.
Run npm uninstall yarn make sure it no longer is listed in your package.json
Delete the yarn.lock file if there is one
If in linux (similar for others I guess):
cd project_directory
Run "npm uninstall yarn"
rm -rf .yarn
rm .yarnrc.yml
rm yarn.lock
in package.json: delete "yarn" lines
in .gitignore (if present): delete "yarn" lines
in README.md (if present): change "yarn" to "npm"
run "grep -irl yarn ." to find any other references
I'm using yarn berry and heroku and consistently getting the error:
➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
Which suggests that my lockfile does not contain all my listed dependencies. In the yarn docs it says this is easily solved by running yarn install and pushing new lockfile to git. However I've tried this, tried with fresh node_modules, etc with no luck.
Has anyone else experienced this issue using yarn berry + heroku?
My repo is a monorepo using workspaces.
I was able to workaround by setting the env-var YARN_ENABLE_IMMUTABLE_INSTALLS to false, as suggested here.
This is likely a bug in Yarn Berry. I've reported it here: https://github.com/yarnpkg/berry/issues/2948
UPD: I have created a fresh local clone of the repo from GitHub, ran yarn install in it, and it did produce changes in yarn.lock. Committing those changes resolved the CI issue, so disabling YARN_ENABLE_IMMUTABLE_INSTALLS is no longer necessary for me.
The original local repo showed a clean git status, so I still believe it is a bug.
UPD 2: My problem was that one of the Yarn worspaces was checked into git as a git submodule (I have probably created it with a nested .git/ folder and then deleted it). As a result, the workspace content, including a child package.json was not committed into the repo, it only existed in my local repo and not on the remote and CI.
After removing the git submodule and checking the workspace into the repo properly, the YN0028 error stopped happening.
If your ENV doesn't contain any CI variables:
Then it could be your yarn config:
Run yarn config get enableImmutableInstalls and see if it's enabled.
(you can also check why it is enabled by running yarn config --why and looking for enableImmutableInstalls).
If it is true, then run yarn config set -H enableImmutableInstalls false to set the setting's value globally (or without the -H argument to set it only in your current project)
I ran across the same issue. I resolve dit by deleting my cache and then reinstalling the dependencies.
The yarn.lock file was then modified by the time the reinstall had completed.
I believe this may have been because I checked in the cache folder initially, and then reverted it. Not sure if this then caused a discrepancy between my local environment and the checked-in repo.
I have a nativescript project where I deleted the hooks and platform folder to run a tns install again. This time the hooks folder never came back.
How do I get the hooks back? It seems to be causing problems where my app doesn't refresh correctly anymore when I make changes to typescript files.
Just delete node_modules folder and run npm i and the hooks will be recreated.
rm -rf node_modules platforms hooks
npm i
A quick question about yarn and yarn.lock in a team setting. When someone updates yarn.lock in git, what is the procedure for developers?
Does yarn automatically figure out that the lock file is newer than node_modules and "figure it out", or do people remove their local node_modules and rerun yarn install?
Yarn won't do any check on node_modules folder when yarn.lock is updated via VCS.
To align node_modules folder with the dependencies listed in yarn.lock, there is no need to delete the folder. Run yarn command instead.