Files

T

fargo 1a822493ba format: apply repo prettier (3.8.1) to the folded skills tree

963 markdown files reformatted with the repository's pinned prettier so
pnpm format:check covers the folded tree like every other repo file.

The formatter's embedded-language pass also normalized code fences
(TS semicolons, closed HTML tags in examples, lowercased CSS hex colors,
one renumbered list that skipped an index). Alphanumeric token deltas vs
the fold commit were audited file-by-file; all are formatter-equivalent
markup normalizations plus the four sanitized skills.

2026-08-19 14:37:17 -05:00

2.5 KiB

Raw Blame History

Suspense is Experimental and API May Change

Rule

<Suspense> is an experimental feature in Vue 3. The API is not guaranteed to reach stable status and may change before it does. Plan for potential breaking changes when using Suspense in production applications.

Why This Matters

Relying heavily on experimental features in production code creates maintenance risk. If the API changes, refactoring could be substantial. The Suspense API has been experimental since Vue 3's initial release (over 4 years) and developers have reported frustrations with bugs and restrictions.

Bad Code

<script setup>
// Building critical application infrastructure on experimental API
// without fallback strategy
</script>

<template>
  <!-- Core navigation depends entirely on Suspense -->
  <Suspense>
    <RouterView />
    <template #fallback>
      <GlobalLoadingScreen />
    </template>
  </Suspense>
</template>

Good Code

<script setup>
import { ref } from 'vue';

// Prepare fallback loading strategy
const isLoading = ref(false);

// Can toggle between Suspense and manual loading if needed
const useSuspense = true;
</script>

<template>
  <!-- Document that this uses experimental API -->
  <!-- Consider: Suspense is experimental - monitor Vue releases -->
  <Suspense v-if="useSuspense">
    <RouterView />
    <template #fallback>
      <GlobalLoadingScreen />
    </template>
  </Suspense>

  <!-- Alternative loading strategy available -->
  <template v-else>
    <GlobalLoadingScreen v-if="isLoading" />
    <RouterView v-else />
  </template>
</template>

Mitigation Strategies

Isolate Suspense usage - Don't spread Suspense throughout the codebase; centralize it
Document usage - Comment where Suspense is used for easy refactoring
Test thoroughly - Suspense edge cases may behave differently across Vue versions
Follow Vue releases - Monitor changelogs for Suspense-related changes
Have a fallback plan - Be ready to implement manual loading states if needed

Key Points

Suspense has been experimental for 4+ years with no stable release date announced
Some developers find it "too buggy or too restrictive" for certain use cases
Consider Vue 2-style loading patterns as a reliable alternative for critical paths
Keep Suspense boundaries minimal and centralized for easier migration

2.5 KiB Raw Blame History