fix: handle path negations when scanning public assets

[danielroe]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Discovered while triaging issue with nuxt/nuxt#26203, we basically weren't handling ignore patterns beginning with ! if they did not also start with !*. (They would end up as part of a directory name.)

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pi0]

Would you mind to add regression test to fixture?

[danielroe]

Will do 💹

Investigating it actually seems that fast-glob does not support negative patterns within ignore (upstream issue). That is a pretty big issue, IMHO.

What do you think about custom ignore patterns per publicAssets dir? In Nuxt, we never want to ignore any build output in dist/client/_nuxt but want the user to be able to ignore patterns in their ~/public directory, for example.

Alternatively, investigating another approach ...

[danielroe]

Okay, I think we're good to go here, using include rather than ignore patterns allows us to support negated ignore patterns without breaking current behaviour.

[pi0]

Nice changes!