Jacob MacDonald

This is a known limitation right now - there are several issues here that would have to be resolved to make it feasible. - We have global require.js config that...

Fwiw, one common internal strategy is to only serve one app with DDC during development, and serve the others with dart2js (they will run/load faster too).

@UnikZ the `$dart*` globals are going to be a problem, although a solvable one. That isn't the dart sdk (the sdk is a require module, `dart_sdk`), its some global state...

Interesting - in general it is best to always reference the implicit `packages` directory that is directly under the first top level dir. I am actually surprised that `` works

Just for some context, regardless of build system support, you always want to reference resources through the exact same uri for caching purposes. The easiest way to ensure that is...

I think we should leave it open as this does sound like a legitmate bug :) I believe we actually don't create nested packages dirs at all when we create...

> It seems that all heavy code is the same for build_resolvers 0.1.1 Yes, we started with a wholesale copy because we want to add performance optimizations that are not...

> The only way I see for it to be quadratic is if _performResolve is invoked once for each asset too. Is that what is happening? If you run codegen...

We did fix the devtools issue here - @kevmoo did we want to do a more general thing? I am not so sure given that ddc does generally work.

Sure, can we close the issue (if we are waiting for new issues anyways, we can just use those)