You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2022. It is now read-only.
However the dar t-runtime Docker first only adds the pubspec file and then runs pub get before adding the rest of the project directory. This prevents the pub get from finding the private library.
Why is it done in this order?
The text was updated successfully, but these errors were encountered:
The dart-runtime base image is intended for the simple case where you just pull packages from pub. In your situation with local packages as well you can use the dart-runtime-base base image. It requires a bit more configuration in terms of the Dockerfile to provide, but gives the flexibility to use local packages. Take a look at the documentation, to see if that fits your needs.
Consider you ship your app with a private library as a dependency. You don't want to publish that to pub.
What I do is add a git submodule to
./modules/private-library
and add a dependency:However the dar t-runtime Docker first only adds the pubspec file and then runs pub get before adding the rest of the project directory. This prevents the pub get from finding the private library.
Why is it done in this order?
The text was updated successfully, but these errors were encountered: