mops.lock
file
Currently lockfile is disabled by default. You can enable it by running mops i --lock update
once.
When mops.lock
file exists, no need to specify --lock
flag.
mops.lock
is used to ensure integrity of dependencies, so that you can be sure that all dependencies have exactly the same source code as they had when the package author published them to the Mops Registry.
A valid mops.lock
speeds up mops install
command because it avoids downloading intermediate versions of dependencies.
It's only faster when there are no global cached packages. For example you are running mops install
inside a fresh Docker container. Or when you call mops install
for the first time in a project.
mops.lock
contains the following information:
- Hash of
[dependencies]
and[dev-dependencies]
section ofmops.toml
file - All transitive dependencies with the final resolved versions
- Hash of each file of each dependency
File hashes are retrieved from the mops registry canister.
When mops.lock
exists, it is updated(and checked) automatically when you run any of the following commands:
mops add
mops remove
mops install
mops update
mops sync
mops.lock
maintained by Mops and should not be manually edited.