@jasonshimmy/vite-plugin-cer-app 0.23.2 → 0.24.0

package/.github/copilot-instructions.md

@@ -1,169 +0,0 @@
----
-applyTo: '**'
----
-
-You are an expert in TypeScript, JavaScript, HTML, CSS. Your task is to produce the most optimized and maintainable code, following best practices and adhering to the principles of clean code and robust architecture.
-
-## Objective
-
-- Create a Web Component Runtime solution that is not only functional but also adheres to the best practices in performance, security, and maintainability.
-- When implementing features, prioritize simplicity and clarity in the codebase.
-- When communicating with the user, you don't need to ask for permission before making cleanups or optimizations. Instead, focus on delivering a solution that is efficient and easy to understand.
-
-## Commands to Know
-
-- `npm run build`: Builds the project for production.
-- `npm run dev`: Starts the development server with hot-reloading.
-- `npm test`: Runs the test suite using Vitest.
-- `npm test:watch`: Runs the test suite using Vitest in development watch mode.
-- `npm run test:coverage`: Generates a code coverage report.
-
-## Code Style and Structure
-
-- ALL CODE MUST BE: lightweight, developer friendly, strongly typed, performant, and scalable.
-- Write concise, technical TypeScript code with accurate examples.
-- Use functional and declarative programming patterns; avoid classes.
-- Prefer iteration and modularization over code duplication.
-- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
-- Structure files: exported component, subcomponents, helpers, static content, types.
-- Use lowercase with dashes for directory names (e.g., `components/auth-wizard`).
-- Use kebab-case for file names (e.g., `auth-wizard.ts`).
-- Avoid using "this" keyword in functional components.
-- Prefer pure functions and avoid side effects.
-- Use immutable data structures where possible.
-- Use JSDoc comments for functions and components to improve IDE intellisense.
-
-## Markdown Documentation
-
-All documentation written in the docs directory should be:
-
-- In Markdown format
-- Structured with clear headings and subheadings
-- Include code examples where applicable
-- Use consistent terminology and phrasing
-- Be 100% accurate with the actual code implementation
-- Be easy to read and understand
-- Be concise and to the point
-- Use emojis for titles
-
-## Naming Conventions
-
-- Use lowercase with dashes for directories (e.g., components/auth-wizard).
-- Favor named exports for components.
-
-## TypeScript Usage
-
-- Use strict TypeScript for all code; prefer interfaces over types.
-- Avoid enums; use maps instead.
-- Use functional components with TypeScript interfaces.
-- Never use "any" type; always prefer strongly typed definitions.
-
-## Syntax and Formatting
-
-- Use the "function" keyword for pure functions.
-- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.
-
-## UI and Styling
-
-- Generate Custom Elements using our lib/index.ts for components and styling.
-- Implement responsive design; use a mobile-first approach.
-
-## Performance Optimization
-
-- Use TypeScript and JavaScript best practices to ensure high performance.
-- Always favor tree-shaking and code splitting.
-- Optimize images: use WebP format, include size data, implement lazy loading.
-
-## Security and Performance
-
-- Implement proper error handling, user input validation, and secure coding practices.
-- Follow performance optimization techniques, such as reducing load times and improving rendering efficiency.
-
-## Testing and Documentation
-
-- Write unit tests for components using Vitest.
-- Provide clear and concise comments for complex logic.
-- Use JSDoc comments for functions and components to improve IDE intellisense.
-
-## Error Handling and Validation
-
-- Prioritize error handling and edge cases:
-  - Use early returns for error conditions.
-  - Implement guard clauses to handle preconditions and invalid states early.
-  - Use custom error types for consistent error handling.
-
-## Key Conventions - NON-NEGOTIABLE
-
-- NEVER GUESS OR ASSUME! Always make informed decisions based on available data in a project.
-- Always use strongly typed TypeScript.
-- Keep code lightweight and modular.
-- Do not use external dependencies.
-- Keep code performant.
-- Keep code secure.
-- Keep code developer friendly and easy to use.
-- Keep code easy to read and understand.
-- Keep code maintainable and scalable.
-- Always write tests for your code.
-- Always follow best practices in coding, security, and performance.
-- Always validate assumptions with actual data.
-- ALWAYS add new unit and e2e/integration tests for any new functionality.
-- ALWAYS document new functionality in the project's documentation files.
-- ALWAYS have the user validate all changes with `npm run validate` and report results back to you.
-- NEVER run Cypress tests yourself. ONLY the user runs Cypress. Always ask the user to run Cypress and report the results.
-- A change can only be considered complete when it meets all the above criteria and has been thoroughly tested and reviewed. THIS IS NON-NEGOTIABLE.
-
-## Feature completion checklist (apply to every new feature or fix)
-
-Before declaring any change complete, ALL of the following must be satisfied:
-
-### Documentation
-- [ ] All new features are documented in the relevant `docs/*.md` file with options, API reference, and examples.
-- [ ] If a composable was added, it has a full entry in `docs/composables.md`.
-- [ ] If the feature affects auto-imports, `docs/configuration.md` is updated.
-- [ ] If the feature affects routing, `docs/routing.md` is updated.
-- [ ] If the feature affects middleware, `docs/middleware.md` is updated.
-- [ ] Documentation is 100% accurate with the actual implementation.
-
-### Unit tests
-- [ ] Vitest unit tests in `src/__tests__/` cover typical usage, edge cases, and error paths.
-- [ ] Existing test coverage has not been reduced.
-
-### E2e tests
-- [ ] Cypress specs in `e2e/cypress/e2e/` cover the feature across all applicable build modes (SPA, SSR, SSG, dev).
-- [ ] Required kitchen-sink fixtures are added to `e2e/kitchen-sink/`.
-- [ ] Cypress is NOT run by the AI — the user runs `npm run e2e` and reports results.
-
-### Auto-imports
-- [ ] New framework composables are added to `FRAMEWORK_IMPORTS` and `FRAMEWORK_IDENTIFIERS` in `src/plugin/transforms/auto-import.ts`.
-- [ ] Auto-import behavior is tested in `src/__tests__/plugin/transforms/auto-import.test.ts`.
-
-### TypeScript
-- [ ] All new code uses strict TypeScript — no `any`, no implicit `any`.
-- [ ] New public types are exported from `src/types/`.
-- [ ] `npm run build` completes without TypeScript errors.
-
-### Validation
-- [ ] `npm run lint && npm test && npm run build` passes clean before asking the user to run Cypress.
-- [ ] User runs `npm run validate` to confirm the full pipeline passes.
-
-## Methodology
-
-1. **System 2 Thinking**: Approach the problem with analytical rigor. Break down the requirements into smaller, manageable parts and thoroughly consider each step before implementation.
-2. **Tree of Thoughts**: Evaluate multiple possible solutions and their consequences. Use a structured approach to explore different paths and select the optimal one.
-3. **Iterative Refinement**: Before finalizing the code, consider improvements, edge cases, and optimizations. Iterate through potential enhancements to ensure the final solution is robust.
-
-## Process:
-
-1. **Deep Dive Analysis**: Begin by conducting a thorough analysis of the task at hand, considering the technical requirements and constraints.
-2. **Planning**: Develop a clear plan that outlines the architectural structure and flow of the solution, using <PLANNING> tags if necessary.
-3. **Implementation**: Implement the solution step-by-step, ensuring that each part adheres to the specified best practices.
-4. **Review and Optimize**: Perform a review of the code, looking for areas of potential optimization and improvement.
-5. **Finalization**: Finalize the code by ensuring it meets all requirements, is secure, and is performant.
-
-### Coding Environment
-
-The user asks questions about the following coding languages:
-
-- TypeScript
-- HTML
-- CSS

package/.github/workflows/publish.yml

@@ -1,257 +0,0 @@
-name: Publish to npm
-
-on:
-  push:
-    branches:
-      - main
-      - develop
-
-permissions:
-  contents: write
-
-concurrency:
-  group: release-${{ github.ref_name }}
-  cancel-in-progress: false
-
-env:
-  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: 'true'
-
-jobs:
-  validate:
-    name: Lint, test, build & e2e
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Use Node.js version from .nvmrc
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: .nvmrc
-          registry-url: 'https://registry.npmjs.org/'
-
-      - name: Cache node modules
-        uses: actions/cache@v4
-        with:
-          path: node_modules
-          key: ${{ runner.os }}-node-${{ hashFiles('package-lock.json') }}
-          restore-keys: |
-            ${{ runner.os }}-node-
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Install Cypress system dependencies
-        run: |
-          sudo apt-get update -y
-          sudo apt-get install -y \
-            libgtk2.0-0t64 libgtk-3-0t64 libgbm-dev libnotify-dev \
-            libnss3 libxss1 libasound2t64 libxtst6 xauth xvfb
-
-      - name: Lint
-        run: npm run lint
-
-      - name: Unit tests
-        run: npm test
-
-      - name: Build library
-        run: npm run build
-
-      - name: E2E tests (SSR)
-        run: xvfb-run --auto-servernum npm run e2e:ssr
-
-      - name: E2E tests (SSG)
-        run: xvfb-run --auto-servernum npm run e2e:ssg
-
-      - name: E2E tests (SPA)
-        run: xvfb-run --auto-servernum npm run e2e:spa
-
-  release:
-    name: Version & publish
-    needs: validate
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      # Resolve the latest tag once so all subsequent steps share the same baseline.
-      - name: Resolve baseline tag
-        id: base
-        run: |
-          LATEST_TAG=$(git tag --sort=-version:refname | head -n1)
-          if [ -z "$LATEST_TAG" ]; then
-            COMMIT_RANGE="HEAD"
-          else
-            COMMIT_RANGE="${LATEST_TAG}..HEAD"
-          fi
-          echo "latest_tag=$LATEST_TAG" >> $GITHUB_OUTPUT
-          echo "commit_range=$COMMIT_RANGE" >> $GITHUB_OUTPUT
-          echo "Baseline tag: ${LATEST_TAG:-'(none - first release)'}"
-          echo "Commit range: $COMMIT_RANGE"
-
-      # Skip release if every commit since the last tag is chore: or docs:
-      # Breaking variants (chore!: / docs!:) are intentionally not excluded.
-      - name: Check if release is needed
-        id: should_release
-        run: |
-          COMMIT_RANGE="${{ steps.base.outputs.commit_range }}"
-          RELEASE_COMMITS=$(git log "$COMMIT_RANGE" --pretty=format:"%s" --no-merges \
-            | grep -vE "^(chore|docs)(\([^)]+\))?:" || true)
-          if [ -z "$RELEASE_COMMITS" ]; then
-            echo "value=false" >> $GITHUB_OUTPUT
-            echo "## Release skipped" >> $GITHUB_STEP_SUMMARY
-            echo "All commits since the last release use \`chore:\` or \`docs:\` prefixes — nothing to publish." >> $GITHUB_STEP_SUMMARY
-          else
-            echo "value=true" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Use Node.js version from .nvmrc
-        if: steps.should_release.outputs.value == 'true'
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: .nvmrc
-          registry-url: 'https://registry.npmjs.org/'
-
-      - name: Cache node modules
-        if: steps.should_release.outputs.value == 'true'
-        uses: actions/cache@v4
-        with:
-          path: node_modules
-          key: ${{ runner.os }}-node-${{ hashFiles('package-lock.json') }}
-          restore-keys: |
-            ${{ runner.os }}-node-
-
-      - name: Install dependencies
-        if: steps.should_release.outputs.value == 'true'
-        run: npm ci
-
-      - name: Build library
-        if: steps.should_release.outputs.value == 'true'
-        run: npm run build
-
-      - name: Configure Git
-        if: steps.should_release.outputs.value == 'true'
-        run: |
-          git config user.name "GitHub Actions"
-          git config user.email "actions@github.com"
-          git remote set-url origin https://x-access-token:${{ secrets.GITHUB_TOKEN }}@github.com/${{ github.repository }}
-
-      # Scan ALL commits since the last tag (not just HEAD) and handle the full
-      # conventional-commits spec: type(scope)!: and BREAKING CHANGE: in body.
-      - name: Determine version bump
-        id: bump
-        if: steps.should_release.outputs.value == 'true'
-        run: |
-          COMMIT_RANGE="${{ steps.base.outputs.commit_range }}"
-
-          SUBJECTS=$(git log "$COMMIT_RANGE" --pretty=format:"%s" --no-merges)
-          FULL_LOG=$(git log "$COMMIT_RANGE" --pretty=format:"%s%n%b" --no-merges)
-
-          BUMP="patch"
-
-          # Major: explicit BREAKING CHANGE footer OR ! after type/scope (e.g. feat!: / feat(scope)!:)
-          if echo "$FULL_LOG" | grep -qE "^BREAKING CHANGE:" || \
-             echo "$SUBJECTS" | grep -qE "^[a-z]+(\([^)]+\))?!:"; then
-            BUMP="major"
-          # Minor: feat: or feat(scope):
-          elif echo "$SUBJECTS" | grep -qE "^feat(\([^)]+\))?:"; then
-            BUMP="minor"
-          fi
-
-          echo "Bump type: $BUMP"
-          echo "bump=$BUMP" >> $GITHUB_OUTPUT
-
-      - name: Generate release notes
-        if: steps.should_release.outputs.value == 'true'
-        run: |
-          COMMIT_RANGE="${{ steps.base.outputs.commit_range }}"
-
-          COMMITS=$(git log "$COMMIT_RANGE" --pretty=format:"- %s (%h)" --no-merges \
-            | grep -vE "^- (release:|chore: update changelog)" || true)
-
-          if [ -z "$COMMITS" ]; then
-            COMMITS="- No changes since last release"
-          fi
-
-          echo "$COMMITS" > commits.txt
-
-      - name: Bump version
-        id: version
-        if: steps.should_release.outputs.value == 'true'
-        run: |
-          BUMP="${{ steps.bump.outputs.bump }}"
-          if [[ "${{ github.ref_name }}" == "develop" ]]; then
-            NEW_VERSION=$(npm version prerelease --preid=beta -m "release: %s [skip ci]")
-          else
-            NEW_VERSION=$(npm version "$BUMP" -m "release: %s [skip ci]")
-          fi
-          echo "version=$NEW_VERSION" >> $GITHUB_OUTPUT
-          git push --follow-tags
-
-      - name: Create release and update changelog
-        if: steps.should_release.outputs.value == 'true'
-        run: |
-          VERSION="${{ steps.version.outputs.version }}"
-          PREV_TAG="${{ steps.base.outputs.latest_tag }}"
-          COMMITS=$(cat commits.txt)
-          DATE=$(date +"%Y-%m-%d")
-
-          if [ -n "$PREV_TAG" ]; then
-            CHANGELOG_LINK="**Full Changelog**: https://github.com/${{ github.repository }}/compare/${PREV_TAG}...${VERSION}"
-          else
-            CHANGELOG_LINK="**Full Changelog**: https://github.com/${{ github.repository }}/commits/${VERSION}"
-          fi
-
-          RELEASE_NOTES=$(printf '## Release %s\n\n### Changes\n%s\n\n%s' \
-            "$VERSION" "$COMMITS" "$CHANGELOG_LINK")
-
-          # Update or create CHANGELOG.md
-          if [ ! -f CHANGELOG.md ]; then
-            printf "# Changelog\n\nAll notable changes to this project will be documented in this file.\n\n" > CHANGELOG.md
-          fi
-
-          {
-            head -3 CHANGELOG.md
-            printf "## [%s] - %s\n\n%s\n\n" "$VERSION" "$DATE" "$COMMITS"
-            tail -n +4 CHANGELOG.md
-          } > CHANGELOG.tmp && mv CHANGELOG.tmp CHANGELOG.md
-
-          git add CHANGELOG.md
-          git commit -m "chore: update changelog for ${VERSION} [skip ci]" || true
-          git push
-
-          # Use python3 for safe multi-line JSON encoding (avoids sed escaping pitfalls)
-          ESCAPED_BODY=$(printf '%s' "$RELEASE_NOTES" | python3 -c "import sys,json; print(json.dumps(sys.stdin.read()))")
-
-          if [[ "${{ github.ref_name }}" == "develop" ]]; then
-            PRERELEASE="true"
-            RELEASE_NAME="${VERSION} (Beta)"
-          else
-            PRERELEASE="false"
-            RELEASE_NAME="${VERSION}"
-          fi
-
-          curl -fsSL -X POST \
-            -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
-            -H "Accept: application/vnd.github.v3+json" \
-            https://api.github.com/repos/${{ github.repository }}/releases \
-            -d "{\"tag_name\":\"${VERSION}\",\"name\":\"${RELEASE_NAME}\",\"body\":${ESCAPED_BODY},\"prerelease\":${PRERELEASE}}"
-
-      - name: Publish to npm
-        if: steps.should_release.outputs.value == 'true'
-        run: |
-          if [[ "${{ github.ref_name }}" == "develop" ]]; then
-            npm publish --tag beta
-          else
-            npm publish
-          fi
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

package/.nvmrc

@@ -1 +0,0 @@
-v22.18.0

package/CHANGELOG.md

@@ -1,236 +0,0 @@
-# Changelog
-
-All notable changes to this project will be documented in this file.
-## [v0.23.2] - 2026-04-25
-
-- fix: add siteUrl configuration for canonical links and robots.txt generation (05c53ca)
-
-## [v0.23.1] - 2026-04-17
-
-- fix: fix useContentSearch loading state, debounce, and automatic retry on fetch failure (4d0207a)
-
-## [v0.23.0] - 2026-04-17
-
-- feat: enhance useContentSearch with loading state and update related tests (d1cee0e)
-
-## [v0.22.0] - 2026-04-16
-
-- feat: add customColors support for jitCss configuration and implement related tests (b8061ef)
-
-## [v0.21.4] - 2026-04-16
-
-- fix: update path resolution for auto-imported components to be relative from .cer/ (633a241)
-
-## [v0.21.3] - 2026-04-13
-
-- fix: enhance content layer with automatic component registration from markdown (62bcc04)
-
-## [v0.21.2] - 2026-04-13
-
-- fix: enhance dev mode logging in runtime and update dependencies (57a5a7c)
-
-## [v0.21.1] - 2026-04-13
-
-- fix: broken test (19540bd)
-- fix: ensure catch all only throws errors if one is actually encountered, enhance content-driven routing and catch-all page handling in documentation (a1ea900)
-
-## [v0.21.0] - 2026-04-12
-
-- feat: add support for numeric ordering prefixes in content paths and update related tests (ffb0bc8)
-
-## [v0.20.5] - 2026-04-12
-
-- fix: enhance hydration handling and data caching in usePageData and routing middleware (305ae7f)
-
-## [v0.20.4] - 2026-04-11
-
-- fix: enhance SSR and SSG support with improved data handling and dev mode configurations (d1783af)
-
-## [v0.20.3] - 2026-04-11
-
-- fix: update content layer documentation and enhance plugin generation logic for SSR compatibility (a5bca33)
-
-## [v0.20.2] - 2026-04-11
-
-- fix: correct loader error handling and improve data fetching in SSR/SSG modes (d225a99)
-- docs: add Content Layer section to README for Markdown/JSON support (376a990)
-
-## [v0.20.1] - 2026-04-11
-
-- fix(content): add fallback title and description extraction from Markdown body (9bab321)
-
-## [v0.20.0] - 2026-04-11
-
-- feat(content): implement file-based content layer with Markdown/JSON support (#1) (c6ef0f7)
-- chore: update dependencies for @jasonshimmy/custom-elements-runtime and typescript-eslint (15095bc)
-
-## [v0.19.3] - 2026-03-29
-
-- fix: bump versions in generated package.json files and update the cer dependency for development (bf1014d)
-
-## [v0.19.2] - 2026-03-28
-
-- fix: add plugin DSD test cases and ensure shared component registry in SSR (ee3fffb)
-
-## [v0.19.1] - 2026-03-28
-
-- fix: add entry-server.ts generation for SSR support in dev server (2f102c8)
-
-## [v0.19.0] - 2026-03-28
-
-- feat: implement observability hooks for SSR requests and responses, including error handling feat: inform developers when private config is used in a public context (44b592c)
-- chore: enhance type definitions with detailed comments across composables and types (e5c1963)
-
-## [v0.18.2] - 2026-03-28
-
-- fix: correct vite-plugin-cer-app version in generated package.json files (ae1ccc1)
-
-## [v0.18.1] - 2026-03-28
-
-- fix: update dependencies in package.json templates for SPA, SSG, and SSR (5729fe1)
-
-## [v0.18.0] - 2026-03-28
-
-- chore: remove dead file (e01aab3)
-- feat: production readiness hardening (5f64c49)
-
-## [v0.17.1] - 2026-03-28
-
-- fix: update dependencies and improve error handling in server templates (0f12ef5)
-
-## [v0.17.0] - 2026-03-27
-
-- feat: add component code-splitting and tests (db7c4c7)
-
-## [v0.16.0] - 2026-03-27
-
-- feat: add internationalization (i18n) support with locale-aware routing (a38407c)
-- docs: add defineOAuthProvider helper and tests for OAuth configuration test: enhance useRoute and useCookie tests for better error handling test: implement tests for defineServerMiddleware functionality test: add tests for OAuth routes in generateServerApiCode test: improve useFetch tests with refresh functionality test: update useHead tests for new script handling (797ef05)
-- docs: update authentication, components, composables, configuration, data loading, head management, middleware, plugins, routing, testing, use-fetch, and use-state documentation for clarity and accuracy (322d181)
-
-## [v0.15.0] - 2026-03-26
-
-- feat: implement useState composable for globally-keyed reactive state management (f8aae38)
-- docs: update inaccuracies (69b807d)
-
-## [v0.14.1] - 2026-03-26
-
-- fix: downgrade typescript (0278d24)
-- fix: add missing dts definitions for composables chore: update dependencies and improve type declarations (546c99c)
-
-## [v0.14.0] - 2026-03-25
-
-- feat: add programmatic navigation and route handling (37a583b)
-
-## [v0.13.1] - 2026-03-22
-
-- fix: optimize imports in Cloudflare and Netlify adapters to remove unused handler export (cc74ce3)
-
-## [v0.13.0] - 2026-03-22
-
-- feat: implement streaming Web API Response support in Cloudflare and Netlify adapters (bfe00e3)
-
-## [v0.12.1] - 2026-03-22
-
-- fix: add meta.hydrate support for route hydration strategies and implement related tests (0513743)
-
-## [v0.12.0] - 2026-03-22
-
-- feat: implement ISR support with isrHandler for SSR fallback in Cloudflare, Netlify, and Vercel adapters (ddcc4d4)
-
-## [v0.11.0] - 2026-03-22
-
-- feat: add Cloudflare Pages adapter for SSR and SSG support (2734c26)
-
-## [v0.10.0] - 2026-03-22
-
-- feat: add adapters for Vercel and Netlify deployment platforms (7112bf6)
-
-## [v0.9.0] - 2026-03-21
-
-- feat: add useCookie and useSeoMeta composables with tests (6536902)
-
-## [v0.8.0] - 2026-03-21
-
-- feat: add middleware support and enhance runtime configuration (78ef4d2)
-
-## [v0.7.0] - 2026-03-21
-
-- feat: add per-route render strategies and error handling in ISR (d76fb89)
-
-## [v0.6.0] - 2026-03-21
-
-- feat(ssr): switch server entry from renderToStringWithJITCSSDSD to renderToStreamWithJITCSSDSD for true incremental streaming (cca67d8)
-
-## [v0.5.0] - 2026-03-21
-
-- feat: add runtime configuration support and ISR enhancements (847cd25)
-
-## [v0.4.6] - 2026-03-21
-
-- fix: merge extraneous templates (7a859bd)
-
-## [v0.4.5] - 2026-03-21
-
-- fix: remove the dsd config option since we always want it on anyway. (3698886)
-
-## [v0.4.4] - 2026-03-21
-
-- fix: bootstrap .cer/tsconfig.json during config loading for improved resolution (f8bda65)
-
-## [v0.4.3] - 2026-03-21
-
-- fix: fix DSD config and update FOUC tests to DSD correctness tests and enhance assertions (a8d36a3)
-- chore: update eslint (5a367e0)
-
-## [v0.4.2] - 2026-03-21
-
-- fix: update dependencies in project templates to latest versions (1390724)
-
-## [v0.4.1] - 2026-03-21
-
-- fix: update app entry point to use virtual module path /@cer/app.ts across templates and tests (139abaf)
-
-## [v0.4.0] - 2026-03-20
-
-- feat: implement useInject composable for consistent value injection across SPA, SSR, and SSG fix: cer app hidden directory issue (f614e92)
-
-## [v0.3.0] - 2026-03-20
-
-- feat: add default .gitignore templates for SPA, SSR, and SSG projects fix: remove unused streaming ssr option fix: generated .cer directory to get out of the way of the user (8656788)
-
-## [v0.2.0] - 2026-03-20
-
-- feat: introduce generated directory for app files and HTML (c8fdcdd)
-
-## [v0.1.6] - 2026-03-20
-
-- fix: update CLI usage instructions to include --package flag for create-cer-app (457114d)
-
-## [v0.1.5] - 2026-03-20
-
-- fix: use vite plugin for light dom jit css fix: update incorrect docs fix: fix the plugin config (c32cf6a)
-
-## [v0.1.4] - 2026-03-20
-
-- fix: fixed many issues across the plugin fix: added e2e tests to ensure functionality works across build types fix:improve documentation (fb24d84)
-
-## [v0.1.3] - 2026-03-19
-
-- fix: FOUC in ssr and ssg (e4fb53d)
-
-## [v0.1.2] - 2026-03-19
-
-- fix(build): fix SSR and SSG build modes (23d5363)
-
-## [v0.1.1] - 2026-03-18
-
-- fix: rename vite-plugin-cer-app usage to @jasonshimmy/vite-plugin-cer-app (60c4bdf)
-
-## [v0.1.0] - 2026-03-18
-
-- fix: add nvmrc (7065201)
-- feat: add publishing capability (812152b)
-- initial commit (43a8365)
-
-