And I would be led to believe I’d need to use can-dynamic-import and {{#if isResolved}}, which doesn’t seem to be the case because the above seems to work fine. Is the above method/syntax explained somewhere in the docs? UPDATE: After some testing it seems like when you add the can-tag attribute it essentially causes can-import to behave like can-dynamic-import with an {{#if isResolved}} check. If that’s literally what happens might be worth adding a note about that to the https://canjs.com/doc/can-view-import.can-tag.html documentation? ALSO: It seems then it would make more sense to use can-tag with can-dynamic-import instead of can-import, wouldn’t it? Or maybe this was a concession or decision to make can-tag turn can-import into a dynamic import? I think it could be explained in the docs either way.

Oh, okay, so you’d have to use {{#if isResolved}} with <can-import></can-import> because it literally adheres to the Dynamic Import docs. It didn’t register with me when @justinbmeyer said:

<can-dynamic-import/> does the same thing <can-import> SOME CONTENT </can-import> does.

I know it’s like adding training wheels, but I think the Dynamic Imports and Static imports pages could be a little clearer about this (essentially just add what Justin wrote above) instead of leaving it up the reader to make an assumption. It’s clear now, but I didn’t think about it that way for whatever reason when encountering the issue.