This PR moves parsing steps inside an Unplugin, instead of the root scope of the Nuxt module.
This allows supporting HMR.
The PR in its current state supports reparsing components on-save, I get the output file (.nuxt/component-meta.mjs) to refresh on each changes, with proper updates.
It needs fixes on HMR before merging, but I can already see few issues:
We can't pass a string to createComponentMetaCheckerByJsonConfig
That would be very helpful to support generating metas from transformed components and not their only the content of the file. That can be useful if the project contains any plugin that may alter the content of or Githubissues.
Githubissues is a development platform for aggregating issues.
This PR moves parsing steps inside an Unplugin, instead of the root scope of the Nuxt module.
This allows supporting HMR.
The PR in its current state supports reparsing components on-save, I get the output file (
.nuxt/component-meta.mjs) to refresh on each changes, with proper updates.It needs fixes on HMR before merging, but I can already see few issues:
createComponentMetaCheckerByJsonConfigThat would be very helpful to support generating metas from transformed components and not their only the content of the file. That can be useful if the project contains any plugin that may alter the content of or Githubissues.Githubissues is a development platform for aggregating issues.