Get is one of the commands of the pub tool.
$ pub get [--offline]
$ pub get Got dependencies!
If the system cache
doesn’t already contain the dependencies,
updates the cache,
downloading dependencies if necessary.
To map packages back to the system cache,
this command creates a
Once the dependencies are acquired, they may be referenced in Dart code.
For example, if a package depends on
pub get gets new dependencies, it writes a
lockfile to ensure that future
gets will use the same versions of those dependencies.
Application packages should check in the lockfile to source control;
this ensures the application will use the exact same versions
of all dependencies for all developers and when deployed to production.
Library packages should not check in the lockfile, though, since they’re
expected to work with a range of dependency versions.
If a lockfile already exists,
pub get uses the versions of dependencies
locked in it if possible. If a dependency isn’t locked, pub gets the
latest version of that dependency that satisfies all the version
This is the primary difference between
pub get and
pub upgrade, which always tries to
get the latest versions of all dependencies.
By default, pub creates a
that maps from package names to location URIs.
.packages file, pub used to create
For more information, see the package specification file proposal.
Getting a new dependency
If a dependency is added to the pubspec and then
pub get is run,
it gets the new dependency and any of its transitive dependencies and
updates the mapping in the
However, pub won’t change the versions of any already-acquired
dependencies unless that’s necessary to get the new dependency.
Removing a dependency
If a dependency is removed from the pubspec and then
pub get is run,
it removes the dependency from the
making the dependency unavailable for importing.
Any transitive dependencies of the removed dependency are also removed,
as long as no remaining immediate dependencies also depend on them.
Removing a dependency never changes the versions of any
The system package cache
Dependencies downloaded over the internet, such as those from Git and the Pub site, are stored in a system-wide cache. This means that if multiple packages use the same version of the same dependency, it only needs to be downloaded and stored locally once.
By default, the system package cache is located in the
subdirectory of your home directory (on Mac and Linux),
%APPDATA%\Pub\Cache (on Windows;
the location might vary depending on the Windows version).
You can configure the location of the cache by setting the
environment variable before running pub.
Getting while offline
If you don’t have network access, you can still run
Because pub downloads packages to a central cache shared by all packages
on your system, it can often find previously downloaded packages
without needing to use the network.
However, by default,
pub get tries to go online if you
have any hosted dependencies,
so that pub can detect newer versions of dependencies.
If you don’t want pub to do that, pass it the
In offline mode, pub looks only in your local package cache,
trying to find a set of versions that work with your package from what’s already
Keep in mind that pub generates a lockfile. If the
only version of some dependency in your cache happens to be old,
pub get locks your app to that old version.
The next time you are online, you will likely want to
pub upgrade to upgrade to a later version.
pub get command supports the
command-line argument, as discussed above.
For options that apply to all pub commands, see Global options.