area17 / blast

Storybook for Laravel Blade 🚀
https://dev.to/area17/getting-started-with-blast-storybook-for-laravel-blade-c5c
Apache License 2.0
269 stars 39 forks source link

Install issues with Fresh Laravel 11 #117

Open domthomas-dev opened 6 months ago

domthomas-dev commented 6 months ago

Hi, it's sure, I'm a beginner with StoryBook. I followed the documentation of this package.

I installed a new fresh Laravel 11.

laravel new storybook
composer require area17/blast
php artisan vendor:publish --provider="A17\Blast\BlastServiceProvider" --tag="blast-config" 

I don't know how I should update the config file

If I do this :

php artisan blast:demo

The story is created

If I do :

php artisan blast:launch

or

php artisan blast:launch --install

I have this : Screenshot 2024-03-14 at 18 49 49

and Screenshot 2024-03-14 at 18 48 32

mrtimbrook commented 6 months ago

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.

creed-aderse commented 4 months ago

I have the same issue. The APP_URL is 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:

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?

creed-aderse commented 4 months ago

@domthomas-dev - this worked for me when I changed my APP_URL to include the port => http://localhost:8000