Content-Length: 304247 | pFad | https://github.com/flutter/flutter/issues/136386

7C GitHub Β· Where software is built
Skip to content

"native-assets" feature should surface stdout/stderr from build.dartΒ #136386

@craiglabenz

Description

@craiglabenz

Is there an existing issue for this?

Use case

When using the new native assets feature (dart-lang/sdk#50565 and #129757), the code that invokes build.dart seems to be burying its stdout and stderr.

I think it makes sense that end developers will not want to be bothered by log statements from these build steps during flutter run/build ..., but seeing output / logging statements is important when writing or debugging build.dart.

Proposal

I'm not sure how to differentiate between these two scenarios, but an escape hatch for build.dart authors would be a significant DX improvement.

(similar to dart-lang/sdk#53732)

cc @dcharkes @stuartmorgan

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projectc: proposalA detailed proposal for a change to Flutterteam-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.triaged-toolTriaged by Flutter Tool team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions









      ApplySandwichStrip

      pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


      --- a PPN by Garber Painting Akron. With Image Size Reduction included!

      Fetched URL: https://github.com/flutter/flutter/issues/136386

      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy