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
Pub packages work a bit like NuGet packages in Dart; and live in the packages folder.
The list of packages is stored in pubspec.yaml in the dependencies section. This only lists the packages you directly add; dependencies of dependencies will live in the packages folder even though they're not in this file.
Currently, the folders inside the packages folder (one per package) are symlinks back to a "pub cache" (eg. C:\Users\Danny\AppData\Roaming\Pub\Cache) though this may change in the future.
Additionally, pub creates packages symlinks as subfolders of many other folders (eg. bin, web). This means rendering the entire tree will have a bunch of duplicated folders:
bin
- packages
web
- packages
packages
pubspec.yaml
I think it might be best for us to:
Render the packages folder as the references folder in the current implementation (so it appears at top, and is "special", allowing for future functionality like a pub package search)
Hide all further nested packages folders from the solution tree
Indicate the difference between packages in pubspec.yaml vs those that just exist on disk (indirect dependencies)
The text was updated successfully, but these errors were encountered:
Pub packages work a bit like NuGet packages in Dart; and live in the
packages
folder.The list of packages is stored in
pubspec.yaml
in thedependencies
section. This only lists the packages you directly add; dependencies of dependencies will live in thepackages
folder even though they're not in this file.Currently, the folders inside the
packages
folder (one per package) are symlinks back to a "pub cache" (eg.C:\Users\Danny\AppData\Roaming\Pub\Cache
) though this may change in the future.Additionally, pub creates
packages
symlinks as subfolders of many other folders (eg.bin
,web
). This means rendering the entire tree will have a bunch of duplicated folders:I think it might be best for us to:
packages
folder as thereferences
folder in the current implementation (so it appears at top, and is "special", allowing for future functionality like a pub package search)pubspec.yaml
vs those that just exist on disk (indirect dependencies)The text was updated successfully, but these errors were encountered: