uncenter
uncenter
I just started to upgrade and I am now getting this too... 👀
If you put your filters wrapped in a plugin, as suggested by https://github.com/11ty/eleventy/issues/3114#issuecomment-1826369696 (and originally https://www.lenesaile.com/en/blog/organizing-the-eleventy-config-file/#method-3-adding-another-config-file-as-a-plugin), or just anywhere you have access to `eleventyConfig`, you can access the `eleventyConfig.javascriptFunctions` object...
I would go as far as to say having a `DATA_DIR/content.{js,json}` file should throw an error, and the same for other reserved keywords.
Seems pretty doable: https://github.com/uncenter/11ty-fork/blob/feat/reserved-keyword-global-data-throw/src/TemplateData.js#L330-L336. Not sure how to find what keys are reserved though, those are just manual.
That's why I was just thinking global data for now.
> Minor updates in dependencies must be opted into at the project level, right? Can you elaborate? > Increase in source conflicts Sure, but that's easily resolved and doesn't outweigh...
Thank you for writing this all out! I've been bouncing some of these ideas around for a while and this is a good summary. Some other related issues and commentary...
Great idea. I'm a big fan of using the `public/` directory as the default, that's what I use on my sites.