Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pendingComponent not works on SSR #3915

Open
williamneves opened this issue Apr 2, 2025 · 0 comments
Open

pendingComponent not works on SSR #3915

williamneves opened this issue Apr 2, 2025 · 0 comments

Comments

@williamneves
Copy link

Which project does this relate to?

Start

Describe the bug

Basic pendingComponents or any "server loading" component pending is not working.

It appears that using the start-only configuration (with the CLI --add-on start option) causes the Pending Component not to load, while running without any options in the raw (no add-ons selected) folder works as expected.

I suspect the integration with vinxi is going badly...

Your Example Website or App

https://stackblitz.com/~/github.com/williamneves/ts-loading-test

Steps to Reproduce the Bug or Issue

Bug Reproduction Steps

This document outlines the steps to reproduce a bug observed when launching the application via the CLI.

https://www.loom.com/share/20544987d887491a88ce5ddc244f8afe

How to reproduce:
https://github.com/williamneves/ts-loading-test

Setup

Two project folders are provided:

  • raw: Executed with no additional options.
  • start-only: Executed using the start option (runs the server using vincs).

Steps to Reproduce

  1. Open each folder in separate terminals.

  2. Run the following command in each folder to install dependencies:

    bun install
  3. In the raw folder, run the command:

    bun start
  4. In the start-only folder, run the command:

    bun dev
  5. Open the /loader route in your browser.

  6. Observe the following behavior:

    • In the raw folder, the loader displays the Pending Component.
    • In the start-only folder, the Pending Component is not loaded.

Expected Behavior

The Pending Component should load on the /loader route in both configurations.

Issue Description

It appears that using the start-only configuration (with the CLI --add-on start option) causes the Pending Component not to load, while running without any options in the raw (no add-ons selected) folder works as expected.

Request for Assistance

Please help investigate why the Pending Component fails to load in the start-only configuration and suggest any fixes or workarounds to ensure consistent behavior.

Expected behavior

I spect the same behavior on both, with is load the pending component

Screenshots or Videos

No response

Platform

  • OS: [e.g. macOS, Windows, Linux]
  • Browser: [e.g. Chrome, Safari, Firefox]
  • Version: [e.g. 91.1]

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant