Keeping the lock file in sync
These instructions will help to ensure we don't introduce unwanted changes to the lock file.
Last updated
Was this helpful?
These instructions will help to ensure we don't introduce unwanted changes to the lock file.
Last updated
Was this helpful?
Since we use some private modules alongside the public monorepo, we have some special requirements when dealing with lock file changes. This can be confusing for and there's around it as well.
The rule of thumb is: As long a we don't introduce new packages (either in a package.json or monorepo package) there shouldn't be any lock file changes in a core contributor local environment.
Make sure you're on main
Make sure you have private submodules initialized and updated
Run yarn install to see if there are lock file diffs
Please refer to the section in our .