You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MWDelaney
changed the title
Eleventy 1.0.1-canary.3 tries to process my config files even though I've tried to tell it not to
Eleventy 1.0.1-canary.3 tries to process my config files even though I've told it not to
Mar 8, 2022
Weird.
I was able to reproduce in 1.0.1-canary.3 and 2.0.0-canary.2, but not in 1.0.0.
But if I remember correctly, I was seeing the error in my log was "./src/config/filters.js"
There are a few different ways to opt out processing a template. Note that permalink: false does not opt out of processing (only prevents writing a template to disk) and is superfluous if you’re already ignoring a template.
Typically you’d added a glob to via standard ignore conventions (.eleventyignore or eleventyConfig.ignores): https://www.11ty.dev/docs/ignores/
But, in this specific case, you can return a falsy value from the compile function in your custom template language options. AND we had a regression in the fix for #2217 for this specific issue, so I appreciate you filing it! Definitely want to get this patched for 1.0.1.
Describe the bug
I believe this is due to the intricacies of my setup, but here we go anyway:
On the ZeroPoint dev branch I've configured two custom template languages,
scss
andjs
.Upgrading from 1.0 to 1.0.1-canary.3 causes the previously working template language configs to fail with errors similar to the following:
This appears to be because Eleventy is ignoring the json file I put in the config directory which had been working to exclude
config
in 1.0.This is a difficult situation to describe helpfully so please let me know what I can do to better illuminate the issue.
To Reproduce
Steps to reproduce the behavior:
npm install
to install the updated dependenciesnpm run dev
Expected behavior
Eleventy 1.0.1 should ignore the javascript files in
config
like 1.0 didEnvironment:
Thanks!
The text was updated successfully, but these errors were encountered: