New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
feat(nuxt): allow remote sources for islands#21592
Conversation
🔗 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
Hi 👋 (this pr has been sleeping for a while now...)
This should be considered as HIGHLY experimental
This PR opens the door to remote islands and introduce a newfallback slot forNuxtIslands which will show up if the component failed to fetch the island component
This feature can be enabled like this:
exportdefaultdefineNuxtConfig({experimental:{componentIslands:'local+remote'}})
📝 Checklist
- I have linked an issue or discussion.
- I have updated the documentation accordingly.
Tested with multiple tunnel locally. I wonder if its possible to test it within e2e fixtures |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.