docs
  1. Storefront SDKs
  2. @scayle
  3. Storefront-navigation

@scayle/storefront-navigation

0.4.0

Minor Changes

  • [Navigation] Added composables and RPC methods for accessing Navigation V2 API data in Nuxt applications.
    Two new composables are now available for easy access to navigation data:
    • useNavigations() - Fetches all navigation trees using the Navigation V2 API:
    • useNavigationsByReferenceKey() - Fetches a specific navigation tree by its reference key:

    Both composables leverage the underlying RPC system with built-in caching support. The RPC methods getAllNavigations and getNavigationsByReferenceKey are automatically registered when the module is installed, providing server-side data fetching with automatic caching using the Storefront cache system.
    The composables follow the standard useRpc pattern, supporting reactive parameters, loading states, and error handling.

0.3.3

Patch Changes

  • Cleaned up README.md and added CONTRIBUTING.md. No functional changes.

0.3.2

Patch Changes

  • Updated SCAYLE Resource Center references

0.3.1

Patch Changes

  • Use latest [email protected] for build. Compatibility with previous version has not changed and is specified via package peerDependencies and Nuxt compatibility flag.

0.3.0

Minor Changes

  • Extended useHeaderNavigation, useFooterNavigation, useSimpleHeaderNavigation, and useSimpleFooterNavigation to accept a second treeName parameter. This parameter can be used to override the default name used to fetch the Navigation Tree.

0.2.0

Minor Changes

  • Update to @nuxt/module-builder@1. This version of Nuxt Module Builder is ESM-only, so CommonJS (.cjs) files will no longer be built or distributed with the package. However as of Nuxt 3, only esm is used so this should not have any impact as this module does not support Nuxt 2.

0.1.0

Minor Changes

  • Initial release of @scayle/storefront-navigation. This package provides utilities for working with Navigation features within the SCAYLE Storefront Boilerplate. It includes the following composable functions.
    • useHeaderNavigation
    • useFooterNavigation
    • useSimpleHeaderNavigation
    • useSimpleFooterNavigation

    Additionally, a isNavigationItemCategoryActive utility function is provided which can be used to determine if a navigation item represents the active category.