Bret Little

Generally it is considered safe to do the following: ``` js $timeout(() => { $scope.$apply(() => { if (!controller.$pristine) { controller.$setViewValue(''); } }); }, 0, false); ``` By using `$timeout`...

@domenic that's easy when not using import maps. But how do I do that when using import maps? As far as I can tell, `import('lodash?retry=1')` isn't supported.

Also, because import maps can't be dynamically changed post resolution, I also can't dynamically change the import map to point to a new URL with a query parameter.

@guybedford it seems as though, when using native modules defined in an import map, the best option is to keep track of `navigator.onLine` and only request the module when the...

@guybedford generally I would agree, but I think there is still an edge case to handle due to: > However, service workers are not available on first load. Thus, they...

I think some sort of API like that would make sense. Whether or not it gets added to the spec, 🤷‍♀️, but I figure this issue could stay open to...

Agreed with @joeldenning. If the browser has never evaluated `import('some-lib')`, then why would it be bad to interpret a new package map that defines `some-lib` even _after_ other modules have...

Yeah, `preact-compat` works fine. I was hoping to not use the compatibility layer though.

This is a case where monorepos are useful :) Maybe if I get time, I'll put together a mono repo implementation

@juanpprieto > I noticed a layout shift because the price is not optimistic. I would maybe add adding or $0 to prevent the vertical shift Yeah I was wondering about...