Description
Steps to Reproduce
Hi guys,
I've recently converted our mobile project into web. I'm in the process of adapting packages and dependencies, but realized it's taking much more time to properly debug issues in web compared to mobile.
One of the reasons is the following:
As you can see in the above stack, every single line is a .js line, which makes it hard to understand which of the 5 calls to getApplicationDocumentsDirectory()
is causing the exception (this is just an example - I know that path provider does not work for web). Clicking on the hyperlink opens up the browser and does nothing.
I'd expect a similar behaviour as in flutter-mobile, where we get the particular dart line that caused the exception. We can even click on it and go straight to the file-line mentioned in the stack trace.
Flutter Doctor
[√] Flutter (Channel stable, 2.10.4, on Microsoft Windows [Version 10.0.19044.1645], locale pt-PT)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
X cmdline-tools component is missing
Run `path/to/sdkmanager --install "cmdline-tools;latest"`
See https://developer.android.com/studio/command-line for more details.
X Android license status unknown.
Run `flutter doctor --android-licenses` to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.
[√] Chrome - develop for the web
[X] Visual Studio - develop for Windows
X Visual Studio not installed; this is necessary for Windows development.
Download at https://visualstudio.microsoft.com/downloads/.
Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 4.2)
[√] VS Code (version 1.66.1)
[√] VS Code, 32-bit edition (version 1.32.3)
[√] Connected device (3 available)
[√] HTTP Host Availability