Files which are both within .eleventyignore and addPassthroughCopy are copied initially but not updated

[groenroos]

Inadvertently, some of the CSS / JS assets I wanted to build via Vite ended up caught in an .eleventyignore path pattern.

This wasn't noticed immediately though, because when initially running the build (whether for production, or with --serve) these assets will still build as normal.

But, when using --serve, these assets will not be watched for changes, and thus, never get re-built after the initial build, until Eleventy is terminated and restarted.

I'm not entirely sure whether the ideal behaviour for assets matching .eleventyignore patterns would be to be always built, or to never be built at all... but the current behaviour of them building successfully once, and then never again, definitely feels undesirable to me.

[KiwiKilian]

Thanks for the report.

Could you please give a minimal reproduction? It's really hard guessing your setup. I understand the main problem, but there are many variables like how are the paths setup, how does it play with passthrough copy, which version are you on...

[groenroos]

Sure! This one's actually pretty easy, I was able to reproduce it in the example/ folder;

1. Create .eleventyignore in the example/ folder, with src/assets/ as the contents
2. Run npx @11ty/eleventy --serve
3. Make any visible change in src/assets/main.css
4. The CSS will not be rebuilt
5. Terminate and restart npx @11ty/eleventy --serve
6. The CSS will be built with the new change

[KiwiKilian]

Thanks! This is happening without the plugin being involved. Not sure what's the best approach, rather not have the files ever copied or throwing an error?

@zachleat could you please move this to 11ty/eleventy?