-
-
Notifications
You must be signed in to change notification settings - Fork 500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
template dependency changes not propagating through to built output #3338
Comments
Almost certain this is a duplicate of #3270, which shipped with |
I saw that one right after I hit submit, via #3337! But unfortunately after upgrading I don't see any changes.
I cleared
|
You’re right—it’s a bug! Milestoning to 3.0 |
Dependencies weren’t being invalidated when used in an 11ty.js Layout file, so it was a problem in our layout caching (not the JS piece as I expected!) Shipping with 3.0.0-alpha.15 |
Operating system
macOS Sonoma 14.5 (23F79)
Eleventy
@11ty/eleventy ^3.0.0-alpha.13
Describe the bug
My markdown file
index.md
uses a layout file_includes/layouts/html.11ty.js
which in turn references_includes/components/table.11ty.js
.When I change either
.11ty.js
file, it triggers a a rebuild and the console output reports:But in this case, the resulting HTML file does not reflect the changes to
table.11ty.js
. However, if I instead edithtml.11ty.js
, it reflects changes to that file (but still does not show the latest from the table component).Both
11ty.js
files are nested at the same depth inside_includes
and nothing is explicitly mentioned in the configuration regarding watch targets. I just rely on the built-in behavior of monitoring the_includes
directory.Reproduction steps
cross-env DEBUG=Eleventy* eleventy --serve
_includes/components/table.11ty.js
_site/index.html
and see the changes are not thereExpected behavior
I expect that the edit would be reflected in the output without having to restart eleventy.
Reproduction URL
https://github.com/marisademeglio/eleventy-issue-3338
Screenshots
No response
The text was updated successfully, but these errors were encountered: