Output can be forced by writing the logger to stderr.

[MichealReed]

Currently, dart is suppressing the stdout, we can override this or a user can override it in the build hook by streaming records from the logger to stderr.

    logger!.onRecord.listen((record) {
      stderr.writeln(record.message);
    });

dart-lang/sdk#53732

[rainyl]

Well, it's helpful, I also meet the problem but I just throw exceptions at debug points to see the logs :(

Maybe we can allow developers to provide a logger instance to the builder.

[MichealReed]

Even if they provide a logger, it will not work. Dart is currently only showing stderr output, so we must pipe the process output to the global stderr for it to show.

stderr.addStream(process.stdout);
stderr.addStream(process.stderr);

or when passing the logger to run

  await builder.run(
    input: input,
    output: output,
    logger:
        Logger('')
          ..level = Level.ALL
          ..onRecord.listen((record) => stderr.writeln(record)),
  );

[rainyl]

or when passing the logger to run

  await builder.run(
    input: input,
    output: output,
    logger:
        Logger('')
          ..level = Level.ALL
          ..onRecord.listen((record) => stderr.writeln(record)),
  );

Yes, package developers can pass a logger this way to show the logs.

With dart-lang/native#39 finished, we can let users to decide whether to show detailed logs,

native_assets:
  defines:
    example_package:
      verbose: true

And inside example_package/hook/build.dart, maintainer can decide whether to use

Logger('')..level = Level.ALL..onRecord.listen((record) => stderr.writeln(record))

according to verbose.