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
It looks like Storybook Server can't access the application. If you open the network tab in your dev tools you'll see the request to your application for the component view. You can right click that and open in a new tab. That will show you the error in your application.
The most common cause for this is that the APP_URL in your .env is incorrect.
Blast uses env('STORYBOOK_SERVER_HOST', env('APP_URL')) . '/storybook_preview', for the URL to generate the views in storybook so you can either define the env var STORYBOOK_SERVER_HOST or use APP_URL.
Installation
You can get started by installing Blast using:
composer require area17/blast
This will:
Create a stories and a data directory for your story Blade files and any associated data
Publish assets used by Blast to the application's public directory
Create a route from which to load your component examples
I don't see any routes being created.
@domthomas-dev - were you ever able to get this to work?
Activity
mrtimbrook commentedon Mar 14, 2024
It looks like Storybook Server can't access the application. If you open the network tab in your dev tools you'll see the request to your application for the component view. You can right click that and open in a new tab. That will show you the error in your application.
The most common cause for this is that the
APP_URLin your.envis incorrect.Blast uses
env('STORYBOOK_SERVER_HOST', env('APP_URL')) . '/storybook_preview',for the URL to generate the views in storybook so you can either define the env varSTORYBOOK_SERVER_HOSTor useAPP_URL.creed-aderse commentedon May 21, 2024
I have the same issue. The
APP_URLis correct.What I am seeing in the documentation here: https://dev.to/area17/getting-started-with-blast-storybook-for-laravel-blade-c5c is this section:
I don't see any routes being created.
@domthomas-dev - were you ever able to get this to work?
creed-aderse commentedon May 21, 2024
@domthomas-dev - this worked for me when I changed my
APP_URLto include the port =>http://localhost:8000