pub_util 0.0.3

  • README.md
  • Installing
  • Versions
  • 43

pub_util Build Status Build status on windows

pub_util is a utility that can help list and update globally installed outdated Dart packages.

The hope is that this functionality will eventually be available in the standard pub global command.

Installation

pub global activate pub_util

Usage

pub_util can list all and outdated packages and update outdated packages.

  1. List all globally installed packages
pub_util -l
  1. List all outdated global packages
pub_util -o
  1. Update all outdated global packages
pub_util -u

Bugs, Fixes, Enhancements

All feedback, PRs and bug reports are welcome.

1. Depend on it

Add this to your package's pubspec.yaml file:


dependencies:
  pub_util: "^0.0.3"

2. Install it

You can install packages from the command line:

with pub:


$ pub get

with Flutter:


$ flutter packages get

Alternatively, your editor might support pub get or packages get. Check the docs for your editor to learn more.

Version Uploaded Documentation Archive
0.0.3 Dec 2, 2016 Go to the documentation of pub_util 0.0.3 Download pub_util 0.0.3 archive
0.0.2 Dec 2, 2016 Go to the documentation of pub_util 0.0.2 Download pub_util 0.0.2 archive
0.0.1 Dec 2, 2016 Go to the documentation of pub_util 0.0.1 Download pub_util 0.0.1 archive

Analysis

This feature is new.
We welcome feedback.
More details: scoring.

We analyzed this package, and provided a score, details, and suggestions below.

  • completed on Feb 3, 2018
  • Dart: 2.0.0-dev.20.0
  • pana: 0.10.1

Scores

Popularity:
Describes how popular the package is relative to other packages. [more]
0 / 100
Health:
Code health derived from static analysis. [more]
100 / 100
Maintenance:
Reflects how tidy and up-to-date the package is. [more]
66 / 100
Overall score:
Weighted score of the above. [more]
43

Platforms

Detected platforms: Flutter, web, other

No platform restriction found in libraries.

Suggestions

  • Maintain CHANGELOG.md.

    Changelog entries help clients to follow the progress in your code.

  • Fix .analysis_options.

    We were unable to parse .analysis_options.

  • The description is too short.

    Add more detail about the package, what it does and what is its target use case. Try to write at least 60 characters.

  • Package is pre-v1 release.

    While there is nothing inherently wrong with versions of 0.*.*, it usually means that the author is still experimenting with the general direction API.

  • Maintain an example.

    Create a short demo in the example/ directory to show how to use this package. Common file name patterns include: main.dart, example.dart or you could also use pub_util.dart.

  • Use analysis_options.yaml.

    Rename old .analysis_options file to analysis_options.yaml.

  • Enable strong mode analysis.

    Strong mode helps you to detect bugs and potential issues earlier.Start your analysis_options.yaml file with the following:

    analyzer:
      strong-mode: true
    

Dependencies

Package Constraint Resolved Available
Direct dependencies
Dart SDK >=1.13.0 <2.0.0
args ^0.13.7 0.13.7 1.3.0
http ^0.11.3 0.11.3+16
Transitive dependencies
async 2.0.3
charcode 1.1.1
collection 1.14.5
http_parser 3.1.1
path 1.5.1
source_span 1.4.0
string_scanner 1.0.2
typed_data 1.1.5
Dev dependencies
test ^0.12.17