eleventyImport, a front matter configuration option to declare template dependency

[zachleat]

We attempt to glean template dependencies automatically to process templates in the correct order but as an escape hatch this might be nice.

[zachleat]

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open.

View the enhancement backlog here. Don’t forget to upvote the top comment with 👍!

[zachleat]

eleventyImport.collections is an Array of collection or tag names used by the template. This is used to inform both --incremental builds and template build order.

Just as an example, say your blog index page iterates over collections.posts. If you add eleventyImport.collections: ["posts"] to the blog index page data (somewhere in the data cascade), it will rebuild the index page when any of your blog posts are changed.

Shipping with 2.0.0-canary.21

(Renamed for canary 21)

[zachleat]

Docs building to https://www.11ty.dev/docs/data-configuration/ (they point back here for now, sorry!)

[megheaiulian]

Does this support collections added in config with addColection ?
According to the docs we should be able to set anything in it.
if we use:

  config.addCollection("homeSections", async (collection) =>
    collection.getFilteredByGlob("./src/home/**/*").reduce(
      (map, i) => ({
        ...map,
        [i.data.type]: [...(map[i.data.type] ?? []), i],
      }),
      {}
    )
  );

is it then possible to use eleventyImport.collections: ["homeSections"] where needed ?

[zachleat]

@megheaiulian yes exactly—I would expect collection names added via eleventyConfig.addCollection to be eligible there!

[zachleat]

The final docs for this ended up at https://www.11ty.dev/docs/collections/#declare-your-collections-for-incremental-builds

[megheaiulian]

I've tried the example above and had problems with circular dependencies when trying to loop thru a collections.homeSections.services structure in a item of type service('collections.homeSections.service').
It seems to work thou when using collections.services instead.
That homeSections is supposed to be just some syntax sugar to differentiate the purpose of the collections.

[megheaiulian]

Ah in the end what fixed my problem was eleventyExcludeFromCollections.

[monochromer]

I have collection, created with addCollection:

// eleventy.config.js

eleventyConfig.addCollection('articles', (collectionAPI) => {
  return collectionAPI.getFilteredByGlob('src/articles/*/*.md')
})

and data file for article template, that uses collection articles for pagination:

// src/pages/article/article.11tydata.js

module.exports = {
  layout: 'base',

  pagination: {
    data: 'collections.articles',
    size: 1,
    alias: 'article'
  },

  eleventyImport: {
    collections: ['articles']
  }
}

when i change md-file, template doesn't render in incremental mode:

[11ty] File changed: src/articles/one/index.md
[11ty] Wrote 0 files (skipped 32) in 0.03 seconds (v2.0.1)