-
Notifications
You must be signed in to change notification settings - Fork 43
Packages cannot declare which platforms they support #889
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Result of pana check
Edit : finally found a way to solve it |
I have a somewhat related issue: flutter_svg does work on web, but imports dart:io and so it gets marked as not working on web, even though it imports dart:io in a safe manner (it does so in precisely the same way that Flutter itself does for images). |
This has landed, but we still need to get docs updated on https://dart.dev/tools/pub/pubspec |
Missing documentation is fixed with dart-lang/site-www#3793 |
This is done! |
Uh oh!
There was an error while loading. Please reload this page.
With the advent of FFI, there are an increasing number of packages (not platform plugins) that contain only Dart code, but which are designed to work on only certain platforms. This will increase as we add more platforms and transition more code to adopt FFI, since it will be increasingly infeasible for a platform integration package to support the wide range of platforms that Dart itself supports.
As an obvious example, the

win32
package by design only supports Windows, but it doesn't have any means to enumerate that.This leads to customer confusion. For example:
halildurmus/filepicker_windows#9 (comment)
halildurmus/win32#166
One potential solution would be to have an entry in
pubspec.yaml
forsupported_platforms
which would override the detection logic built intopana
and allow plugin authors to explicitly declare which platforms they choose to support.The text was updated successfully, but these errors were encountered: