Jacob MacDonald
Jacob MacDonald
They are supposed to but they can't due to limitations of the prototype. This is unlikely to be fixed, but I am filing this for posterity.
This may soon become a blocker for experimenting with these features, given that formatting is required in places where we want to land macros.
See https://github.com/dart-lang/ecosystem/blob/main/pkgs/firehose/README.md
For instance with package:build_runner the build script wants to intercept the first SIGINT and wait for the current build to complete. On the second SIGINT it will actually exit right...
# Environment - `pub version` or `flutter pub version`: 2.15.0-233.0.dev # Problem I was trying to migrate the test package to use a `.pubignore` file to work around the issue...
This has been coming up in the context of `flutter_web`, which requires a globally activated package (`webdev`). If you globally activate it using the flutter SDK - like `flutter packages...
## Proposal The package_config.json file permits storing extra data in both package entries as well as top level fields, but there is no general way to utilize this today, because...
Today the `any` identifier allows any version (stable or pre-release). Changing that behavior would be a breaking change, hence the proposal for a new `stable` identifier. As a concrete use...
The `macros` package will be a pub package, which only re-exports APIs from the `_macros` package, which is an SDK vendored package. I can generate docs for the macros package...
For dart, the docs are at [api.dart.dev](https://api.dart.dev). For flutter, they are at [api.flutter.dev](https://api.flutter.dev), but for pub, they are at [pub.dev/documentation](https://pub.dev/documentation/). I can never remember the pub link though and end...