You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a pub transformer is running on it's own package the Dart source files that it loads have package: imports changed to /package/.
The conversion from package: to /package/ should be an internal detail- if required for isolate loading then assets fetched via transform.readAsInputString should use a different transfer mechanism.
These imports leak when the transformer modifies the source code- if the transformer does not remove the /package/ then this propagates down the chain.
The text was updated successfully, but these errors were encountered:
We could probably make [transform.readAsInputString] avoid this, but it would likely be a lot of work and further degrade the "pub serve"/"pub build" startup time. The "/package/" workaround will go away when issue dart-lang/sdk#12474 is fixed, so I'm going to mark this blocked.
<img src="https://avatars.githubusercontent.com/u/2152569?v=3" align="left" width="96" height="96"hspace="10"> Issue by blois
Originally opened as dart-lang/sdk#17156
When a pub transformer is running on it's own package the Dart source files that it loads have package: imports changed to /package/.
The conversion from package: to /package/ should be an internal detail- if required for isolate loading then assets fetched via transform.readAsInputString should use a different transfer mechanism.
These imports leak when the transformer modifies the source code- if the transformer does not remove the /package/ then this propagates down the chain.
The text was updated successfully, but these errors were encountered: