Webdev serve - Time consuming
- Dominant language
- Dart
- Stars
- 224
- Forks
- 94
- Avg merge
- 7h 14m
- Merged PRs (30d)
- 2
Description
Hello,
I’m opening this issue because I’m really confused about the time wasted switching to dart2.
Indeed, I work hard to migrate a big project from dart1. The project has around thirty sub-projects and each tiny change in a sub-project in the hierarchy requires a recompilation before I can see the result in the browser. Even a simple little ‘;’ takes monster time. We cannot afford to wait 5-10 minutes for the slightest change even with the automatic re-build of
> webdev serve
Also, in its time, debugging was relatively fast via chromium because there was no compilation. Now, using webstorm, the stacktrace is abominable because it only fatally shows incomprehensible javascript.
Seriously, when you work in a project without any other dependence, no worries, it's great !
But in a big project like ours, it's a real calamity.
How do you manage this ?
Unless I miss something, are there ways to speed up the process?
Currently it is a totally indigestible process.
update : dart --version
Dart VM version: 2.7.1 (Thu Jan 23 13:02:26 2020 +0100) on "windows_x64" (Windows 10)
Thank u !
Contributor guide
Research direction
Start with webdev serve on the reported Dart 2.7.1 and Windows 10 setup, using the multi-project arrangement described, and measure rebuild time after a tiny change. Compare the Chromium debugging path with WebStorm’s JavaScript stack traces. The issue does not define what done looks like, so first establish a reproducible bottleneck and get a maintainer-confirmed scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100