Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(anchorLinks): add useRuntimeConfig imports #1605

Merged
merged 1 commit into from Oct 16, 2022
Merged

fix(anchorLinks): add useRuntimeConfig imports #1605

merged 1 commit into from Oct 16, 2022

Conversation

nobkd
Copy link
Contributor

@nobkd nobkd commented Oct 16, 2022

πŸ”— Linked issue

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 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)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

My new local projects always get the following error in edge channel:

500
useRuntimeConfig is not defined
View full log

Webpage:

500

useRuntimeConfig is not defined

at _sfc_main.setup (./node_modules/@nuxt/content/dist/runtime/components/Prose/ProseH1.js:39:23)
at callWithErrorHandling (./node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:157:22)
at setupStatefulComponent (./node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:7135:29)
at setupComponent (./node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:7090:11)
at renderComponentVNode (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:172:17)
at renderVNode (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:299:22)
at renderComponentSubTree (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:263:13)
at renderComponentVNode (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:188:16)
at renderVNode (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:299:22)

Console:

[Vue warn]: Unhandled error during execution of setup function 
  at <ProseH1 id="nuxt-content" >

This is obviously caused by the new anchorLinks option (--> the config checking in the heading prose components), so I added the necessary import.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@netlify
Copy link

netlify bot commented Oct 16, 2022

βœ… Deploy Preview for nuxt-content ready!

Built without sensitive environment variables

Name Link
πŸ”¨ Latest commit 6f73296
πŸ” Latest deploy log https://app.netlify.com/sites/nuxt-content/deploys/634c70c535cf9700086edfd6
😎 Deploy Preview https://deploy-preview-1605--nuxt-content.netlify.app
πŸ“± Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@farnabaz farnabaz merged commit 005fdfd into nuxt:main Oct 16, 2022
@nobkd nobkd deleted the fix/anchorLinks-import-error branch October 16, 2022 21:06
@farnabaz farnabaz mentioned this pull request Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants