Merge pull request #401 from Weaverse/june-2025

Author: paul-phan

.github/workflows/check.yml

@@ -25,7 +25,7 @@ jobs:
       - name: Setup Biome
         uses: biomejs/setup-biome@v2
         with:
-          version: 2.0.0-beta.6 # todo: change to stable if stable version is released
+          version: 2
       - name: Run Biome
         run: biome ci .
 

.lefthook/pre-commit

@@ -57,6 +57,9 @@ call_lefthook()
     elif mise exec -- lefthook -h >/dev/null 2>&1
     then
       mise exec -- lefthook "$@"
+    elif devbox run lefthook -h >/dev/null 2>&1
+    then
+      devbox run lefthook "$@"
     else
       echo "Can't find lefthook in PATH"
     fi

.lefthook/prepare-commit-msg

@@ -57,6 +57,9 @@ call_lefthook()
     elif mise exec -- lefthook -h >/dev/null 2>&1
     then
       mise exec -- lefthook "$@"
+    elif devbox run lefthook -h >/dev/null 2>&1
+    then
+      devbox run lefthook "$@"
     else
       echo "Can't find lefthook in PATH"
     fi

biome.json

@@ -1,5 +1,6 @@
 {
-  "$schema": "https://biomejs.dev/schemas/2.0.0-beta.6/schema.json",
+  "root": true,
+  "$schema": "https://biomejs.dev/schemas/2.0.0/schema.json",
   "extends": ["./packages/biome/biome.json"],
   "vcs": {
     "enabled": true,
@@ -15,7 +16,8 @@
       "!**/build/**",
       "!**/.turbo/**",
       "!**/templates/**",
-      "!**/package-lock.json"
+      "!**/package-lock.json",
+      "!**/app/styles/app.css"
     ]
   },
   "linter": {

docs/guides/third-party-integration.md

@@ -10,6 +10,7 @@ published: true
 # Third-party Integration
 
 ## Table of Contents
+
 - [Third-party Integration](#third-party-integration)
   - [Table of Contents](#table-of-contents)
   - [Introduction](#introduction)
@@ -165,19 +166,20 @@ For third-party services that offer a REST or GraphQL API, Weaverse's loader pat
    ```tsx
    // app/sections/api-widget/index.tsx
    import type { ComponentLoaderArgs } from '@weaverse/hydrogen'
+
 import { createSchema } from '@weaverse/hydrogen'
 import { forwardRef } from 'react'
    import { Section, type SectionProps } from '~/components/section'
-   
+
    type ApiWidgetData = {
      resourceId: string
      itemsToShow: number
    }
-   
+
    export const loader = async ({ weaverse, data }: ComponentLoaderArgs<ApiWidgetData>) => {
      const { fetchWithCache, env, storefront } = weaverse
      const { resourceId, itemsToShow = 5 } = data
-     
+
      if (!resourceId) return { items: [] }
 
      try {
@@ -197,13 +199,13 @@ import { forwardRef } from 'react'
        return { items: [], error: true }
      }
    }
-   
+
    type ApiWidgetProps = SectionProps<Awaited<ReturnType<typeof loader>>> & ApiWidgetData
-   
+
    const ApiWidget = forwardRef<HTMLElement, ApiWidgetProps>((props, ref) => {
      const { loaderData, resourceId, itemsToShow, ...rest } = props
      const { items, error } = loaderData || { items: [] }
-     
+
      if (error) {
        return (
          <Section ref={ref} {...rest}>
@@ -227,9 +229,9 @@ import { forwardRef } from 'react'
        </Section>
      )
    })
-   
+
    export default ApiWidget
-   
+
    export let schema = createSchema({
      type: 'api-widget',
      title: 'API Widget',
@@ -260,6 +262,7 @@ import { forwardRef } from 'react'
        }
      ]
    })
+
    ```
 
 ## Data Fetching Patterns
@@ -283,6 +286,7 @@ export const loader = async ({ weaverse, data }: ComponentLoaderArgs<WidgetData>
 ```
 
 Benefits:
+
 - API keys remain secure on the server
 - Reduced JavaScript bundle size
 - Better performance for initial page load
@@ -320,6 +324,7 @@ export function AnalyticsClient({ trackingId }) {
 ```
 
 Use this approach when:
+
 - The integration requires browser-specific APIs
 - The third-party service needs to track user interactions
 - The widget needs to be initialized after the page loads
@@ -367,6 +372,7 @@ function ClientInteractivity({ initialData, settings }) {
 ```
 
 This pattern is ideal for:
+
 - Review systems that need initial content rendered server-side but allow client-side submissions
 - Interactive widgets that need to show initial data quickly but then become interactive
 - Progressive enhancement scenarios
@@ -468,6 +474,7 @@ export let schema = createSchema({
 ```
 
 The implementation:
+
 1. Defines a schema with an API key input that triggers revalidation when changed
 2. Uses a loader to securely fetch reviews from the Ali Reviews API
 3. Structures the component to render Ali Review data
@@ -540,6 +547,7 @@ export default ReviewIndex;
 ```
 
 This approach:
+
 1. Leverages existing Hydrogen route data instead of making additional API calls
 2. Separates the display components from the data fetching logic
 3. Optimizes performance by reusing already fetched data
@@ -815,6 +823,7 @@ Common issues and their solutions:
    - Look for rate limiting or quota issues
 
    Solution:
+
    ```tsx
    try {
      // Make your API call here
@@ -836,6 +845,7 @@ Common issues and their solutions:
    - Ensure your component handles the absence of data gracefully
 
    Solution:
+
    ```tsx
    const Widget = forwardRef((props, ref) => {
      const { loaderData } = props
@@ -859,6 +869,7 @@ Common issues and their solutions:
    - Use client components with careful boundaries
 
    Solution:
+
    ```tsx
    'use client'
    import { useEffect, useState } from 'react'

docs/guides/weaverse-component.md

@@ -12,6 +12,7 @@ published: true
 Weaverse Components are the building blocks of your Hydrogen theme. They combine React's component model with Weaverse's powerful schema system to create customizable, performant sections for your storefront. This guide provides a comprehensive overview of how to create, configure, and optimize Weaverse components.
 
 ## Table of Contents
+
 - [Getting Started](#getting-started)
 - [Core Concepts](#core-concepts)
 - [Component Structure](#component-structure)
@@ -290,13 +291,15 @@ export let schema = createSchema({
 ## Component Types
 
 ### 1. Content Sections
+
 - Hero sections (images, videos)
 - Text blocks and rich content
 - Media galleries and sliders
 - Feature sections
 - Testimonial sections
 
 ### 2. E-commerce Components
+
 - Product displays
 - Collection grids
 - Related products
@@ -305,6 +308,7 @@ export let schema = createSchema({
 - Checkout components
 
 ### 3. Interactive Elements
+
 - Forms and newsletters
 - Reviews and testimonials
 - Maps and location displays
@@ -745,12 +749,14 @@ export async function loader({ context }: ComponentLoaderArgs) {
 ```
 
 **Weaverse's `fetchWithCache`** is a convenient utility that simplifies cached data fetching from external APIs:
+
 - Available through `context.weaverse.fetchWithCache`
 - Automatically handles JSON parsing
 - Applies the specified caching strategy
 - Provides a cleaner syntax compared to Hydrogen's native `fetchSync`
 
 Hydrogen provides several caching strategies out of the box:
+
 - `CacheNone()`: No caching, always fetches fresh data
 - `CacheShort()`: Short-term caching (a few minutes)
 - `CacheLong()`: Long-term caching (1 day by default)
@@ -1287,4 +1293,3 @@ Remember that great components are:
 - **Maintainable**: They follow clean code principles and are well-documented
 
 As you build your Weaverse components, focus on creating a consistent user experience while enabling flexibility and customization through the schema system.
-

package.json

@@ -24,7 +24,7 @@
     "ci": "biome ci --changed"
   },
   "devDependencies": {
-    "@biomejs/biome": "^2.0.0-beta.6",
+    "@biomejs/biome": "^2.0.0",
     "@changesets/cli": "^2.29.4",
     "@types/node": "24.0.0",
     "@types/react": "19.1.7",

packages/biome/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @weaverse/biome
 
+## 1.3.0
+
+### Minor Changes
+
+- update biome to v2
+
 ## 1.2.4
 
 ### Patch Changes

packages/biome/biome.json

@@ -1,6 +1,6 @@
 {
   "root": false,
-  "$schema": "https://biomejs.dev/schemas/2.0.0-beta.6/schema.json",
+  "$schema": "https://biomejs.dev/schemas/2.0.0/schema.json",
   "linter": {
     "rules": {
       "style": {

packages/biome/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@weaverse/biome",
-  "version": "1.2.4",
+  "version": "1.3.0",
   "description": "Biome configuration for Weaverse",
   "scripts": {
     "test": "echo \"Error: no test specified\" && exit 1"
@@ -20,7 +20,7 @@
   },
   "homepage": "https://github.com/Weaverse/weaverse#readme",
   "dependencies": {
-    "@biomejs/biome": "2.0.0-beta.6"
+    "@biomejs/biome": "^2.0.0"
   },
   "files": [
     "biome.json"