You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
start-only: Executed using the start option (runs the server using vincs).
Steps to Reproduce
Open each folder in separate terminals.
Run the following command in each folder to install dependencies:
bun install
In the raw folder, run the command:
bun start
In the start-only folder, run the command:
bun dev
Open the /loader route in your browser.
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
The text was updated successfully, but these errors were encountered:
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:
Steps to Reproduce
Open each folder in separate terminals.
Run the following command in each folder to install dependencies:
In the raw folder, run the command:
In the start-only folder, run the command:
Open the
/loader
route in your browser.Observe the following behavior:
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
Additional context
No response
The text was updated successfully, but these errors were encountered: