Resources can depend on other resources

Person in labcoat walking left


A large part of what makes importing non-JavaScript resources compelling is the ability to treat resources as dependencies within an application's module graph. Resources imported as dependencies can be transformed, have their URLs hashed, and their usage can be analyzed and taken into account when performing code splitting.

The benefits of introducing resources into the module graph also generally apply to any subresources present in those resources. For example, a CSS StyleSheet can contain references to images, fonts and other stylesheets, all of which can be treated as dependencies. These tests check to see if non-JavaScript resources have their own dependencies, and whether those dependencies avoid common pitfalls like duplication.

Use the (+) card below & tell us if we missed a capability!

Plant with tall leafs and vines in a pot

Questions or Concerns?

We want to hear from you, let us know how to make this better. Open up a GitHub issue and we’ll track it there. Thanks!

Open a GitHub Issue