schabanbo / pub_manager Goto Github PK

use git blame -L 50,50 README.md

Licenses summery > License Summary

This is a really good product, why stop at dart python needs one until pyproject.toml becomes mainstream, requirements.txt does not
if you can go so far to node even java you can get more downloads!

In my case static analysis shows flutter_background as an unused package. I do not have that in my pubspec.yaml file

On my current project we have a mono-repo with nested flutter projects, so we have ~50 different pubspec.yaml, and none in the project's root.

It doesn't seem like your plugin supports this kind of architecture as I get a blank tab when showing package list.

I think the easiest way to support mono-repos would be to add the possibility to launch the tab on any chosen file (like with right-click or currently opened file)

It is pretty useless without considering dependencies. For instance: It says I'm using http 0.13.6 and it is available 1.1.0. But this is not as simple as that: there is a dependency (signalr_core) that requires http 0.13.6. dart pub outdated will tell me this, by saying that there is a newer version of some package, but the last RESOLVABLE version is not the latest:

╰─ $ dart pub outdated
Showing outdated packages.
[*] indicates versions that are not the latest available.

Package Name Current Upgradable Resolvable Latest

direct dependencies:
http *0.13.6 *0.13.6 *0.13.6 1.1.0

dev_dependencies: all up-to-date.
You are already using the newest resolvable versions listed in the 'Resolvable' column.
Newer versions, listed in 'Latest', may not be mutually compatible.

This

  flutter_i18n: ^0.33.0

will be updated to this

  flutter_i0.34.0n: ^0.33.0

Hi,

I have just installed the extension and noticed an unexpected change. When updating the http package from 1.0.0 to 1.1.0, it changed the pubspec.yaml from

http: ^1.0.0 cached_network_image: git: url: http://github.com/lucasmiranda5/flutter_cached_network_image.git ref: dart3 path: cached_network_image

To this:

http: 1.1.0 cached_network_image: git: url: 1.1.0://github.com/lucasmiranda5/flutter_cached_network_image.git ref: dart3 path: cached_network_image

Notice the start of the URL has changed from http:// to 1.1.0://

Also, the ^ symbol does not persist when updating the version.

On further investigation, it also replaced any URL in comments throughout the whole pubspec.yaml file.

Also when I tried to run it on Windows, I got a service worker error.

Thanks for the extension 👏

Hey, thanks for your extension, I use it daily on my workflow. I don't know if it make sense, but would be great and a lot easier to keep track and update the core stuffs as the on on the title from build.gradle, wr. For newbies it's scaring when you get some conflict because of that.

Some example:

gradle-wrapper.properties

• distributionUrl=https://services.gradle.org/distributions/gradle-8.5-all.zip

dependencies on build.gradle and app/build.gradle

• implementation 'com.google.android.gms:play-services-auth:20.7.0'
• implementation 'com.google.android.gms:play-services-ads:22.5.0'
• implementation(platform("com.google.firebase:firebase-bom:32.5.0"))
• 'com.android.tools.build:gradle:8.2.0'
• 'org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version'
• 'com.google.gms:google-services:4.4.0'
• ext.kotlin_version

I think it will be a good extra to add in your extension.

Hope it will be useful for you. Thanks!

Thank you for the plugin, works really nicely :-)

As I develop, sometime i use so many dependency, so it is helpful if this plugin have feature sortable.

maybe u can add like sorttable.js or tablesorter.js

Thankyou :))

• Make the font smaller (or just use current VSCode settings). It's way too large!
• re add the button in pubspec file

You already have a fantastic button for static analysis for showing unused packages and unused files.

Using flutter build <platform> --analyze-size you could also show how much MB each package contributes to the total build size (after tree-shaking).
For details see: https://docs.flutter.dev/perf/app-size#breaking-down-the-size

Thanks for considering!

This is more a query really - why are these showing up at all?

Thank you for the plugin, works really nicely :-)

As I develop for multiple plattforms, it is helpful to know which package supports which plattform - would this be a feature for this package to have a new column for the supported plattforms? :-)

Thank you!

• Update Button: Adding an "Update" button at the top of the list would be a convenient way to update all outdated packages at once.
• Version Information: The "Latest Version" and "Version" columns could be swapped. Users typically scan from left to right, so seeing the current version first would be more natural.