flutter / flutter/website

[infra] Consider improving build failure error messages

Open
#13,826 1 comment 0 reactions 0 assignees View on GitHub
infra.structure p2-medium
Dominant language
Dart
Stars
3.1k
Forks
3.5k
Avg merge
2d 4h
Merged PRs (30d)
95

Description

### Describe the problem

Currently, when I run `dart run dash_site build` and it fails the output looks like this:

```
$ dart run dash_site serve

Building package executable...
Built dash_site:dash_site.
Running jaspr in static rendering mode.
✓ [CLI] Web compilers started. (3.5s)
✗ [CLI] [ERROR] Failed building web assets. There is probably more output above. (0.9s)
[CLI] [ERROR] Could not start dev server due to build errors.
Terminating web compilers...
```

This doesn't provide any help into where investigate.

### Expected fix

The build error should provide more information, even if its high-level. For example, is there a problem did the scss compiler fail? Or is there an error in a Jaspr component? etc. Just that information would go a long way.

### On which platform(s) did you experience this issue?

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the failure with `dart run dash_site build` or `dart run dash_site serve` and inspect the output around the web compiler failure. Trace how dash_site reports Jaspr and SCSS or other asset-build errors, then make the final message identify the failing stage or component and verify that the output gives actionable investigation context.

Written by the indexing model from the issue text.

Assessment

Tech stack
dart
Domain
build-system, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.