[ ] ๐ 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)
[x] ๐งน Chore (updates to the build process or auxiliary tools and libraries)
[ ] โ ๏ธ Breaking change (fix or feature that would cause existing functionality to change)
๐ Description
I feel like there is a lot going on in the i18n plugin, after looking at Nuxt's source code I noticed some features are separated into plugins, so I tried to do the same here ๐
๐ Linked issue
โ Type of change
๐ Description
I feel like there is a lot going on in the i18n plugin, after looking at Nuxt's source code I noticed some features are separated into plugins, so I tried to do the same here ๐
I also tried another way of reorganizing the plugin logic here https://github.com/nuxt-modules/i18n/pull/3017, but that's a bit more involved.
If refactors like these actually make things harder to read, do let me know, I'm too familiar with the codebase now to notice if that is the case ๐
๐ Checklist