fix: remove setInterval from the presets

[wattanx]

🔗 Linked issue

Fixes: #897

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ 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

The setInterval overridden by Nuxt is auto-imported, so it can no longer be mocked with useFakeTimers.
(setInterval = window.setInterval, but the previous state is retained.)

I think updating the documentation with a method like separating workspaces as shown below is one possible approach, but which would be more appropriate?
https://stackblitz.com/edit/github-agxb9y-slbn4d

[danielroe]

thank you!

should we do this for any of the other polyfills nuxt imports, perhaps?

[wattanx]

Yes, that's correct. requestIdleCallback seems to have similar issues as setInterval.
Adding an option to exclude specific polyfills could be a good approach—for example, something like imports.polyfills. What do you think?

[danielroe]

maybe!

certainly we can avoid the interval polyfill on client side