Skip to content

Conversation

@michaeldyrynda
Copy link
Contributor

We need to account for the fact that the default Bootstrap preset has been extracted to a separate package in laravel/ui and install this, before being able to run the Inertia.js preset over the top of it.

We need to account for the fact that the default Bootstrap preset has
been extracted to a separate package in laravel/ui and install this,
before being able to run the Inertia.js preset over the top of it.
Typically you'll install the composer preset as a dev dependency, and
may remove it for production, but we still need the inertia-laravel
dependency in prod, otherwise everything breaks when it's removed.
@reinink
Copy link
Collaborator

reinink commented Sep 6, 2019

Curious, why do we even need the Bootstrap stuff for Inertia?

@michaeldyrynda
Copy link
Contributor Author

The default views use Bootstrap because that’s what was included with Laravel when the initial version was built.

They’d probably otherwise not be very exciting, or we’d have to make a decision on a) what to style them with or b) whether to include them at all.

@michaeldyrynda
Copy link
Contributor Author

@reinink I've scrapped Bootstrap entirely, pulling in Tailwind (CDN version, to keep dependencies as light as possible).

image

I also found a way (per-Telescope) to inject a service provider into the config/app.php file, in order to setup default asset versioning and shared data.

Copy link
Collaborator

@reinink reinink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love it! Using the CDN is a great way of handing this! 👌

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

Successfully merging this pull request may close these issues.

3 participants