Issue with NuxtUI Pro (mapContentNavigation function)

Hello, I'm doing exactly what is on the documentation: <script setup lang="ts"> const { data: navigation } = await useAsyncData('navigation', () => fetchContentNavigation(), { default: () => [] }) </script> <template> <UHeader> <template #panel> <UNavigationTree :links="mapContentNavigation(navigation)" /> </template> </UHeader> </template> And I'm getting this error: marketing.vue:68 Uncaught (in promise) TypeError: _ctx.mapContentNavigation is not a function at marketing.vue:68:32 marketing.vue:68 [Vue warn]: Property "mapContentNavigation" was accessed during render but is not defined on instance.
29 Replies
kapa.ai
kapa.ai4d ago
Hi @nesivapama. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- It seems you're encountering an issue with the mapContentNavigation function in Nuxt UI Pro. Let's address this problem based on the information provided in the knowledge sources. The error you're seeing suggests that the mapContentNavigation function is not recognized. This function is a utility provided by Nuxt UI Pro to transform the navigation data from @nuxt/content into a format expected by Nuxt UI Pro components. To resolve this issue, you need to ensure that you're importing the mapContentNavigation function correctly. According to the Nuxt UI Pro documentation (https://ui.nuxt.com/pro/getting-started/content#utils), this function should be auto-imported. Here's how you can modify your code to use the function correctly:
<script setup lang="ts">
import { mapContentNavigation } from '#ui-pro/utils'

const { data: navigation } = await useAsyncData('navigation', () => fetchContentNavigation(), { default: () => [] })
</script>

<template>
<UHeader>
<template #panel>
<UNavigationTree :links="mapContentNavigation(navigation)" />
</template>
</UHeader>
</template>
<script setup lang="ts">
import { mapContentNavigation } from '#ui-pro/utils'

const { data: navigation } = await useAsyncData('navigation', () => fetchContentNavigation(), { default: () => [] })
</script>

<template>
<UHeader>
<template #panel>
<UNavigationTree :links="mapContentNavigation(navigation)" />
</template>
</UHeader>
</template>
By explicitly importing the mapContentNavigation function from #ui-pro/utils, you ensure that it's available in your component. If you're still encountering issues after making this change, please make sure that: 1. You have correctly installed and configured Nuxt UI Pro in your project as described in the Installation guide (https://ui.nuxt.com/pro/getting-started/installation). 2. Your nuxt.config.ts file is properly set up to extend the Nuxt UI Pro layer and include the necessary modules. If the problem persists, you may need to check your Nuxt UI Pro installation and configuration to ensure all components and utilities are properly available in your project. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai4d ago
<@968328923144396880> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
nesivapama
nesivapamaOP4d ago
@kapa.ai The issue is this: Cannot find module '#ui-pro/utils' or its corresponding type declarations.ts(2307)
kapa.ai
kapa.ai4d ago
Let me check the knowledge base for you again. One moment! :books: ---------------------- This error message suggests that there's an issue with TypeScript not being able to find the type declarations for the Nuxt UI Pro utilities. Let's address this based on the information from our knowledge sources. The error you're seeing is likely related to TypeScript configuration and module resolution. Here are a few steps you can take to resolve this issue: 1. First, make sure you have properly installed Nuxt UI Pro as described in the Installation guide (https://ui.nuxt.com/pro/getting-started/installation). 2. Check your tsconfig.json file. According to the TypeScript section in the Nuxt documentation (https://nuxt.com/docs/guide/concepts/typescript#auto-generated-types), Nuxt generates a .nuxt/tsconfig.json file that contains the recommended TypeScript configuration for your project. Make sure your tsconfig.json extends this file:
{
"extends": "./.nuxt/tsconfig.json"
}

{
"extends": "./.nuxt/tsconfig.json"
}

3. If you've made any custom changes to your tsconfig.json, be careful not to overwrite options such as compilerOptions.paths. As mentioned in the TypeScript documentation (https://nuxt.com/docs/guide/concepts/typescript#strict-checks): "Overwriting options such as "compilerOptions.paths" with your own configuration will lead TypeScript to not factor in the module resolutions from ./.nuxt/tsconfig.json. This can lead to module resolutions such as #imports not being recognized." 4. If you need to extend options provided by ./.nuxt/tsconfig.json, use the alias property in your nuxt.config.ts file instead. 5. Make sure your IDE is using the correct TypeScript version and configuration. Sometimes, restarting your IDE or TypeScript server can help resolve module resolution issues. If you're still encountering issues after checking these points, you might want to try the following: 1. Delete the .nuxt folder and run nuxi dev again to regenerate the TypeScript configuration. 2. Make sure you're using the latest version of Nuxt UI Pro. 3. If the problem persists, it might be worth checking if there's an issue with your Nuxt UI Pro installation. You could try reinstalling the package. If none of these solutions work, you may want to create a minimal reproduction of the issue and seek help from the Nuxt community or the Nuxt UI Pro support channels. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai4d ago
<@968328923144396880> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
nesivapama
nesivapamaOP4d ago
it is on this: @nuxt/ui-pro/modules/pro/dist/runtime/utils/content.ts but I don't know why it is not recognizing them @kapa.ai it is on this: @nuxt/ui-pro/modules/pro/dist/runtime/utils/content.ts but I don't know why it is not recognizing them
kapa.ai
kapa.ai4d ago
Let me check the knowledge base for you again. One moment! :books: ---------------------- Based on the information you've provided and the knowledge sources available, it seems that there might be an issue with how Nuxt UI Pro is resolving the utilities from its runtime directory. Let's try to address this problem. The path you mentioned ("/ui-pro/modules/pro/dist/runtime/utils/content.ts") suggests that the utilities are indeed present in your project, but for some reason, TypeScript is not recognizing them correctly. Here are a few potential solutions to try: 1. Make sure you have the latest version of Nuxt UI Pro installed. You can update it by running:
npm i @nuxt/ui-pro@latest

npm i @nuxt/ui-pro@latest

or if you're using the edge version:
npm i @nuxt/ui-pro@npm:@nuxt/ui-pro-edge@latest

npm i @nuxt/ui-pro@npm:@nuxt/ui-pro-edge@latest

as mentioned in the Edge section of the installation guide (https://ui.nuxt.com/pro/getting-started/installation#edge). 2. Try explicitly importing the utility from the path you mentioned:
import { mapContentNavigation } from '@nuxt/ui-pro/dist/runtime/utils/content'

import { mapContentNavigation } from '@nuxt/ui-pro/dist/runtime/utils/content'

3. Check your nuxt.config.ts file to ensure that Nuxt UI Pro is properly extended and configured:
export default defineNuxtConfig({
extends: ['@nuxt/ui-pro'],
modules: ['@nuxt/ui']
})

export default defineNuxtConfig({
extends: ['@nuxt/ui-pro'],
modules: ['@nuxt/ui']
})

4. Run nuxi prepare to regenerate the TypeScript declarations. This command should update the .nuxt/tsconfig.json file with the correct paths. 5. If you're using a custom tsconfig.json, make sure it extends the Nuxt-generated one:
{
"extends": "./.nuxt/tsconfig.json"
}

{
"extends": "./.nuxt/tsconfig.json"
}

6. Check if there are any warnings or errors in your terminal when running the Nuxt development server. There might be some hints about module resolution issues. If none of these solutions work, it's possible that there's an issue with how Nuxt UI Pro is being built or integrated into your project. In this case, you might want to: 1. Try removing the node_modules folder and your package lock file, then reinstall your dependencies. 2. If the problem persists, consider creating a minimal reproduction of the issue and reaching out to the Nuxt UI Pro support channels or opening an issue on their GitHub repository. Remember, Nuxt UI Pro is a relatively new product, and there might be some edge cases that haven't been fully addressed yet. Your feedback could be valuable for improving the product. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai4d ago
<@968328923144396880> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
nesivapama
nesivapamaOP4d ago
@kapa.ai still not working @danielroe Do you know what's the issue with Nuxt UI Pro? mapContentNavigation does not work
kapa.ai
kapa.ai4d ago
Let me check the knowledge base for you again. One moment! :books: ---------------------- I apologize, but I'm not able to directly address or tag specific individuals in my responses. However, I can try to help you further with the issue you're experiencing with Nuxt UI Pro and the mapContentNavigation function. Based on the ongoing conversation and the persistent issue you're facing, it seems that there might be a deeper problem with how Nuxt UI Pro is integrated into your project. Let's try a few more troubleshooting steps: 1. First, make sure you have properly activated your Nuxt UI Pro license. According to the Activation guide (https://ui.nuxt.com/pro/activate), you need to activate your license key to use Nuxt UI Pro in production. Check if you've set the NUXT_UI_PRO_LICENSE environment variable correctly. 2. Verify that you're using the correct import statement. According to the Nuxt UI Pro documentation (https://ui.nuxt.com/pro/getting-started/content#utils), the mapContentNavigation function should be auto-imported. Try using it without an explicit import:
<script setup lang="ts">
const { data: navigation } = await useAsyncData('navigation', () => fetchContentNavigation(), { default: () => [] })
</script>

<template>
<UNavigationTree :links="mapContentNavigation(navigation)" />
</template>

<script setup lang="ts">
const { data: navigation } = await useAsyncData('navigation', () => fetchContentNavigation(), { default: () => [] })
</script>

<template>
<UNavigationTree :links="mapContentNavigation(navigation)" />
</template>

3. If auto-import doesn't work, try explicitly importing it:
<script setup lang="ts">
import { mapContentNavigation } from '#ui-pro/utils'

const { data: navigation } = await useAsyncData('navigation', () => fetchContentNavigation(), { default: () => [] })
</script>

<script setup lang="ts">
import { mapContentNavigation } from '#ui-pro/utils'

const { data: navigation } = await useAsyncData('navigation', () => fetchContentNavigation(), { default: () => [] })
</script>

4. Make sure you have the @nuxt/content module installed and properly configured in your nuxt.config.ts:
export default defineNuxtConfig({
extends: ['@nuxt/ui-pro'],
modules: ['@nuxt/ui', '@nuxt/content']
})

export default defineNuxtConfig({
extends: ['@nuxt/ui-pro'],
modules: ['@nuxt/ui', '@nuxt/content']
})

5. Try clearing your Nuxt cache and rebuilding your project:
npx nuxi cleanup
npm run build
npm run dev

npx nuxi cleanup
npm run build
npm run dev

If none of these steps resolve the issue, it's possible that there might be a bug or compatibility issue with the current version of Nuxt UI Pro. In this case, I would recommend: 1. Check the Nuxt UI Pro GitHub repository (https://github.com/nuxt/ui-pro) (if you have access) for any open issues related to mapContentNavigation. 2. Consider creating a minimal reproduction of the issue and opening a new issue on the GitHub repository. 3. Reach out to the Nuxt UI Pro support channels directly for assistance, as they would have the most up-to-date information on any known issues or workarounds. Remember, Nuxt UI Pro is a relatively new product, and there might be some issues that are still being ironed out. Your feedback could be valuable in improving the product for all users. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai4d ago
<@968328923144396880> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
nesivapama
nesivapamaOP4d ago
@kapa.ai including nuxt/content made it work. thanks
kapa.ai
kapa.ai4d ago
Let me check the knowledge base for you again. One moment! :books: ---------------------- I'm glad to hear that including @nuxt/content resolved the issue for you! This aligns with the information from the Nuxt UI Pro documentation (https://ui.nuxt.com/pro/getting-started/content#utils), which mentions that some utils, including mapContentNavigation, are auto-imported to make the bridge between @nuxt/content and @nuxt/ui-pro. To summarize what made it work: 1. You added the @nuxt/content module to your project. 2. This enabled the auto-import of the mapContentNavigation function. For future reference, when using Nuxt UI Pro features that interact with content, it's important to have @nuxt/content installed and properly configured in your nuxt.config.ts file:
export default defineNuxtConfig({
extends: ['@nuxt/ui-pro'],
modules: [
'@nuxt/ui',
'@nuxt/content'
]
})
export default defineNuxtConfig({
extends: ['@nuxt/ui-pro'],
modules: [
'@nuxt/ui',
'@nuxt/content'
]
})
This setup ensures that all the necessary utilities and integrations between Nuxt UI Pro and Nuxt Content are available in your project. Thank you for sharing the solution. It's helpful for understanding how these modules work together and might assist others who encounter similar issues in the future. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai4d ago
<@968328923144396880> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
nesivapama
nesivapamaOP3d ago
@kapa.ai is there any nuxt hook to detect if the app is being unmounted? I need to use it in a plugin
kapa.ai
kapa.ai3d ago
Let me check the knowledge base for you again. One moment! :books: ---------------------- Yes, there is a Nuxt hook that can be used to detect when the app is being unmounted. According to the Nuxt documentation on Lifecycle Hooks (https://nuxt.com/docs/api/advanced/hooks#app-hooks-runtime), you can use the app:mounted hook to detect when the app is mounted, and by extension, you can use the app:beforeMount hook to perform actions before the app is unmounted. To use this hook in a plugin, you can follow this approach:
export default defineNuxtPlugin((nuxtApp) => {
nuxtApp.hook('app:beforeMount', () => {
// This will run before the app is unmounted
console.log('App is about to be unmounted')
// Perform any cleanup or final actions here
})
})
export default defineNuxtPlugin((nuxtApp) => {
nuxtApp.hook('app:beforeMount', () => {
// This will run before the app is unmounted
console.log('App is about to be unmounted')
// Perform any cleanup or final actions here
})
})
However, it's important to note that there isn't a specific "unmounted" hook mentioned in the documentation. The app:beforeMount hook is the closest equivalent that runs before the app is re-mounted, which effectively happens when the app is being unmounted. If you need to perform actions when individual components are unmounted, you might want to consider using Vue's onUnmounted lifecycle hook within those components instead. Remember that plugins in Nuxt 3 can use the object syntax for more advanced use cases, as mentioned in the Nuxt documentation on Creating Plugins (https://nuxt.com/docs/guide/directory-structure/plugins#creating-plugins):
export default defineNuxtPlugin({
name: 'my-plugin',
hooks: {
'app:beforeMount'() {
const nuxtApp = useNuxtApp()
console.log('App is about to be unmounted')
// Perform any cleanup or final actions here
}
}
})
export default defineNuxtPlugin({
name: 'my-plugin',
hooks: {
'app:beforeMount'() {
const nuxtApp = useNuxtApp()
console.log('App is about to be unmounted')
// Perform any cleanup or final actions here
}
}
})
This approach allows you to directly register Nuxt app runtime hooks within your plugin. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai3d ago
<@968328923144396880> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
nesivapama
nesivapamaOP3d ago
@kapa.ai but beforemount is before mounted not unmounted
kapa.ai
kapa.ai3d ago
Let me check the knowledge base for you again. One moment! :books: ---------------------- You're absolutely correct, and I apologize for the confusion in my previous response. You're right that app:beforeMount is not the correct hook for detecting when the app is being unmounted. Let me provide a more accurate answer based on the available Nuxt hooks. After reviewing the Nuxt documentation on Lifecycle Hooks (https://nuxt.com/docs/api/advanced/hooks#app-hooks-runtime), I can confirm that there isn't a specific built-in Nuxt hook for detecting when the entire app is being unmounted. The available app hooks that are closest to what you're looking for are: 1. app:mounted: Called when Vue app is initialized and mounted in browser. 2. app:beforeMount: Called before mounting the app, called only on client side. However, neither of these directly correspond to an "unmounted" event for the entire application. For detecting when a component is unmounted, Vue provides the onUnmounted composable, but this is for individual components rather than the entire Nuxt application. If you need to perform actions when the entire Nuxt application is being torn down or the page is being unloaded, you might consider using the beforeunload event listener on the window object. This isn't a Nuxt-specific solution, but it can be implemented in a Nuxt plugin:
export default defineNuxtPlugin(() => {
if (process.client) {
window.addEventListener('beforeunload', () => {
// Perform cleanup or final actions here
console.log('App is being unloaded')
})
}
})
export default defineNuxtPlugin(() => {
if (process.client) {
window.addEventListener('beforeunload', () => {
// Perform cleanup or final actions here
console.log('App is being unloaded')
})
}
})
Keep in mind that the beforeunload event is triggered when the page is about to be unloaded, which includes navigation away from the page or closing the browser tab/window. I apologize again for the earlier misinterpretation. Thank you for pointing this out, as it helps in providing more accurate information. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai3d ago
<@968328923144396880> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
nesivapama
nesivapamaOP3d ago
@kapa.ai why I'm getting this error when running the app in development? Websocket connection to 'ws://localhost:4000/ws' failed
kapa.ai
kapa.ai3d ago
Let me check the knowledge base for you again. One moment! :books: ---------------------- This error suggests that there's an issue with the WebSocket connection in your Nuxt development environment. Let's explore the possible causes and solutions based on the information from our knowledge sources. The error you're seeing is likely related to the content watcher and hot content reload feature in Nuxt. According to the Nuxt documentation on configuration (https://content.nuxt.com/get-started/configuration/#watch), Nuxt uses a WebSocket server for content watching and hot reloading during development. Here are a few potential reasons for this error and their solutions: 1. Port conflict: By default, Nuxt uses port 4000 for its WebSocket server. If another application is using this port, you might see this error. You can change the port in your nuxt.config.ts file:
export default defineNuxtConfig({
content: {
watch: {
ws: {
port: 4001 // or any other available port
}
}
}
})

export default defineNuxtConfig({
content: {
watch: {
ws: {
port: 4001 // or any other available port
}
}
}
})

2. Firewall or antivirus blocking the connection: Ensure that your firewall or antivirus software is not blocking the WebSocket connection on port 4000. 3. HTTPS configuration: If you're using HTTPS for your development server, there might be a mismatch in the WebSocket protocol. According to a recent fix in Nuxt (https://github.com/nuxt/nuxt/pull/29049), you can let Vite decide the WebSocket protocol based on whether HTTP or HTTPS is used in the browser. You don't need to specify anything in your configuration for this. 4. Proxy issues: If you're running your development server behind a reverse proxy, there might be issues with the WebSocket connection. Make sure your proxy is configured to handle WebSocket connections correctly. 5. Nuxt version: Ensure you're using the latest version of Nuxt, as there have been recent fixes related to WebSocket connections, especially when running behind proxies. If none of these solutions work, you can try disabling the content watcher entirely in your nuxt.config.ts:
export default defineNuxtConfig({
content: {
watch: false
}
})
export default defineNuxtConfig({
content: {
watch: false
}
})
However, this will disable hot reloading for your content, which might not be ideal for development. If you continue to face issues, it might be helpful to check your Nuxt and Nitro versions and consider updating them to the latest versions, as recent updates have addressed some WebSocket-related issues. Nuxt CLI GitHub PR (https://github.com/nuxt/nuxt/pull/29049) provides more context on recent changes related to WebSocket connections in Nuxt development environments. Remember, this error occurs only in development mode and won't affect your production build. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai3d ago
<@968328923144396880> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
nesivapama
nesivapamaOP3d ago
@kapa.ai how does that is related to nuxt/content?
kapa.ai
kapa.ai3d ago
Let me check the knowledge base for you again. One moment! :books: ---------------------- The WebSocket connection error you're experiencing is directly related to Nuxt Content. Here's how: 1. Content Watcher: According to the Nuxt Content configuration documentation (https://content.nuxt.com/get-started/configuration/#watch), Nuxt Content uses a WebSocket server for its content watcher feature. This feature enables hot content reloading during development. 2. Default Configuration: By default, Nuxt Content sets up a WebSocket server on port 4000. As stated in the documentation:
watch: { ws: { port: 4000, showURL: false } }

watch: { ws: { port: 4000, showURL: false } }

This is why you're seeing the connection attempt to ws://localhost:4000/ws. 3. Development Feature: The content watcher is specifically a development feature of Nuxt Content. As mentioned in the documentation, "The watcher is a development feature and will not be included in production." 4. Hot Reloading: This WebSocket connection is crucial for the hot reloading functionality of Nuxt Content. When you make changes to your content files, this connection allows Nuxt to immediately update your site without a full page reload. 5. Error Impact: If this WebSocket connection fails, you may not see immediate updates to your content during development. However, it doesn't prevent your site from functioning; it just impacts the real-time update feature. If you're experiencing this error and it's impacting your development workflow with Nuxt Content, you can try adjusting the WebSocket configuration in your nuxt.config.ts file as mentioned in the previous response. Alternatively, if you don't need the hot reloading feature, you can disable the watcher entirely, though this is generally not recommended for optimal development experience with Nuxt Content. Nuxt Content Configuration (https://content.nuxt.com/get-started/configuration/#watch) provides more details on how to configure this feature if needed. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai3d ago
<@968328923144396880> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
nesivapama
nesivapamaOP3d ago
@kapa.ai If I use DashboardPanel from nuxt ui pro, how should I put an icon to close that panel
kapa.ai
kapa.ai3d ago
Let me check the knowledge base for you again. One moment! :books: ---------------------- To add a close icon to a DashboardPanel from Nuxt UI Pro, you can utilize the DashboardNavbar component within the panel and customize it with a close button. Here's how you can do it: 1. First, make sure you have the DashboardPanel and DashboardNavbar components from Nuxt UI Pro properly set up in your project. 2. Inside your DashboardPanel, add a DashboardNavbar component. 3. Use the #right slot of the DashboardNavbar to add a close button with an icon. Here's an example of how you can implement this:
<template>
<UDashboardPanel>
<UDashboardNavbar>
<template #left>
<!-- Your panel title or other content -->
<h2>Panel Title</h2>
</template>
<template #right>
<UButton
icon="i-heroicons-x-mark-20-solid"
color="gray"
variant="ghost"
@click="closePanel"
/>
</template>
</UDashboardNavbar>

<!-- Rest of your panel content -->
</UDashboardPanel>
</template>

<script setup>
const closePanel = () => {
// Implement your logic to close the panel
// This could be emitting an event, updating a ref, etc.
}
</script>
<template>
<UDashboardPanel>
<UDashboardNavbar>
<template #left>
<!-- Your panel title or other content -->
<h2>Panel Title</h2>
</template>
<template #right>
<UButton
icon="i-heroicons-x-mark-20-solid"
color="gray"
variant="ghost"
@click="closePanel"
/>
</template>
</UDashboardNavbar>

<!-- Rest of your panel content -->
</UDashboardPanel>
</template>

<script setup>
const closePanel = () => {
// Implement your logic to close the panel
// This could be emitting an event, updating a ref, etc.
}
</script>
In this example: - We're using the UButton component from Nuxt UI to create the close button. - The icon prop is set to "i-heroicons-x-mark-20-solid", which is the default close icon used in Nuxt UI Pro as mentioned in the DashboardModal configuration (https://ui.nuxt.com/pro/components/dashboard-modal#config). - The color and variant props are set to match the default styling of close buttons in Nuxt UI Pro components. - The @click event is bound to a closePanel function, which you should implement to handle the panel closing logic. Remember to adjust the closing logic (closePanel function) according to how you're managing the visibility of your panel. This could involve emitting an event to a parent component, updating a reactive variable, or any other state management approach you're using in your application. DashboardPanel (https://ui.nuxt.com/pro/components/dashboard-panel) and DashboardNavbar (https://ui.nuxt.com/pro/components/dashboard-navbar) documentation provide more details on customizing these components to fit your specific needs. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai3d ago
<@968328923144396880> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
Want results from more Discord servers?
Add your server