The current implementation only resolves the options used
to generate the robots.txt statically from nuxt.config.js.
This limits the module's use cases as it is not possible to extend
the config from another nuxt module during static site generation.
Why is the change needed?
The current implementation only resolves the options used to generate the robots.txt statically from nuxt.config.js. This limits the module's use cases as it is not possible to extend the config from another nuxt module during static site generation.
How is the need addressed?
By using the same pattern as @nuxtjs/sitemap do for this feature
What side-effects could the change have?