[content-theme-docs] Render Error thrown on `yarn generate` with default docs theme components
See original GitHub issueVersion
@nuxt/content-theme-docs: v0.10.1 nuxt: v2.15.2 yarn: v1.22.5 node: v14.16.0
Steps to reproduce
yarn create nuxt-content-docs my-project
cd my-project
yarn generate
What is Expected?
The generation should happen without errors. The default theme components should be usable with the generate
command.
What is actually happening?
An render error is throw that the “function or template not defined in component”. This happens with all the default components.
This only happens with the generate
command, yarn dev
renders the component correctly.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
Error Codes | Yarn - Package Manager
A list of Yarn's error codes with detailed explanations. ... Two packages with build scripts have cyclic dependencies. Cyclic dependencies are a can...
Read more >React Native integration guide - Bugsnag docs
The Bugsnag ErrorBoundary allows you to capture React render errors in your application. You can also use the FallbackComponent to display a custom...
Read more >Flow error handler - Product Documentation | ServiceNow
Enable flows to catch errors. Run a sequence of actions and subflows to identify and correct issues. For example, have flows log output...
Read more >@nuxt/content-theme-docs - npm
@nuxt/content-theme-docs. TypeScript icon, indicating that this package has built-in type declarations. 0.11.1 • Public • Published a year ...
Read more >'themeprovider' cannot be used as a jsx component - You.com
Its currently throwing this issue saying that ThemeProvider cannot be used as a JSX component, ... When I run yarn run build I...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
downgrading to “nuxt”: “2.15.6” and “@nuxt/components”: “2.1.8” solved it for me. With yarn use: “resolutions”: { “nuxt”: “2.15.6”, “@nuxt/components”: “2.1.8” } in your package.json
Updating
@nuxt/components
to v2.2.1 may help. https://github.com/nuxt/components/issues/223 I’ve solved it.