Unclear that `config` named export is new in v3.0.0
Nobody has claimed this yet.
- Dominant language
- Nunjucks
- Stars
- 547
- Forks
- 726
- Avg merge
- 2h 23m
- Merged PRs (30d)
- 3
Description
Support for a named config export from configuration files (https://github.com/11ty/eleventy/issues/3246) was first released in v3.0.0, but the only note on https://www.11ty.dev/docs/config-shapes/ says that "Added in v3.0.0: Support for ESM and Asynchronous callbacks was added in Eleventy v3.0." As far as I can tell the config named export isn't ESM-specific or related to async, so maybe a new note should be added or the wording of this note could be changed to:
-Added in v3.0.0: Support for ESM and Asynchronous callbacks was added in Eleventy v3.0.
+Added in v3.0.0: Support for ESM, asynchronous callbacks, and the `config` named export were added in Eleventy v3.0.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the config shapes documentation page linked in the issue and read the existing v3.0.0 note in context. Update the note or add a nearby note so the config named export is explicitly identified as a v3.0.0 feature. Done means the page clearly distinguishes this export from ESM and asynchronous callbacks.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100