How to use my dart packages private and not show on pub dart lang?

Question

I have dart packages that I don't want to publish to pub because of my company agreement. How to use my dart packages for only my company and not show on pub dart lang?

I've looked up on this link https://github.com/dart-lang/pub/issues/1050 but still need more information about that.

Answer 1

If you publish a package to https://pub.dartlang.org it will show up. There is no way around that.

Alternatives.

You can use

• path dependencies to packages stored on a local or network drive for example.
• Git dependencies to packages stored in a Git repository
  • on a local or network drive
  • hosted on GitHub, GitLab, or any other Git server
• run your own private Pub server.

See also

• https://www.dartlang.org/tools/pub/dependencies
• https://github.com/dart-lang/pub_server

Answer 2

local :

To handle that, pub supports path dependencies.

dependencies:
  transmogrify:
    path: /Users/me/transmogrify

This says the root directory for transmogrify is /Users/me/transmogrify.

See : https://www.dartlang.org/tools/pub/dependencies

Answer 3

Günter Zöchbauer answer is correct but he hasn't provided it with examples.

So to use pub/package/lib without publishing on pub.dev :

1. Local - Save in some local folder

dependencies:
  library_name:
   path: /path/to/library_name

---

2. Hosted - Pushed on Github, Gitlab etc.

dependencies:
  library_name:
   git: https://github.com/username/library_name

Or to target exact branch

dependencies:
  library_name:
   git:
    url: https://github.com/username/library_name.git
    ref: dev    #branch name

Or to target exact commit

dependencies:
  library_name:
   git:
    url: https://github.com/username/library_name.git
    ref: e234072340    #commit reference id

Where 'library_name' has to be the same as the 'name' declared in pubspec.yaml of that pub.

Answer 4

You can also let someone else run the pub server (as a service): https://cloudsmith.io/l/dart-repository/

Although it's commercial (paid) for private repositories, it's free for public and open-source repositories. If you're looking for a serverless managed solution, it's the only alternative (as of writing).