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

React Application Not Rendering in StackBlitz WebContainer #3144

Open
soundbapp opened this issue Oct 30, 2024 · 0 comments
Open

React Application Not Rendering in StackBlitz WebContainer #3144

soundbapp opened this issue Oct 30, 2024 · 0 comments

Comments

@soundbapp
Copy link

Description of Bug

Provide a concise description of your bug and your project link (if applicable).
The application is failing to render, resulting in a blank/black screen. The dev server appears to be running (on port 3000) but no content is being displayed.

Environment:

StackBlitz WebContainer
React + Vite application
TypeScript
Tailwind CSS
shadcn/ui components

Console Errors:

Source map error related to WebAssembly instantiation:

Source map error: Error: URL constructor: is not a valid URL.
Resource URL: wasm:https://bolt.new/assets/wasm-CsfmP73Z.js%20line%20%3F%20WebAssembly.instantiate

Multiple partitioned cookie/storage access warnings in third-party contexts

Project Structure:

Using modular component architecture
Proper file organization with components split into logical units
All required dependencies are present in package.json
Configuration files (vite.config.ts, tsconfig.json, etc.) are properly set up

Steps to Reproduce

Start development server with npm run dev
Observe blank screen despite server running
Check console for WebAssembly and cookie-related errors

Expected Behavior

Application should render a comment section UI with:
Comment input field
Reaction emoji bar
List of comments with replies
Avatar components
Interactive buttons

Actual Behavior:

Screen remains blank/black
No visible UI elements
Server is running but content isn't rendering

Possible Root Causes:

WebAssembly loading issue in WebContainer environment
Path aliasing configuration mismatch
Missing or incorrect module imports
Third-party context isolation affecting component rendering

Screenshots/Screencast

Screenshot 2024-10-29 at 8 41 20 PM Screenshot 2024-10-29 at 8 41 32 PM

Additional Context/Questions
I have burned through a lot of tokens over the issue. This appears to be an environment-specific issue related to WebContainer's handling of WebAssembly and module loading, rather than an application code issue.

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

No branches or pull requests

1 participant