11ty / 11ty/eleventy-plugin-bundle
Add `importBundleForUrl` to merge bundles (useful as a stopgap for collections use)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 83
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
As described in https://github.com/11ty/eleventy/issues/3730 any use of the HTML content from Collections items will not automatically inform the dependency graph (and include any dependent bundle contents).
It might be helpful to add a importBundleFromUrl or mergeBundleFromUrl method to merge bundles. This might be a bigger lift given that content does not include HTML from Eleventy Layouts (but the bundles as currently configured would?)
It might be easier to use eleventyImport.collections as a way to merge bundles too. https://www.11ty.dev/docs/data-configuration/#advanced
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 by reading issue #3730 and the advanced data configuration documentation, then compare how Collections content, Eleventy Layouts, and configured bundles contribute to the dependency graph. The issue does not identify files or tests, and completion remains open between adding a URL-based bundle merge method and extending eleventyImport.collections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100