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

[2.x] Simplify Tailwind installation #1060

Merged
merged 2 commits into from
May 30, 2022
Merged

[2.x] Simplify Tailwind installation #1060

merged 2 commits into from
May 30, 2022

Conversation

jessarcher
Copy link
Member

This PR simplifies the Tailwind installation in Jetstream and is the counterpart of this Breeze PR:

  • Uses the @tailwind directive instead of @import, per the standard installation guide.
  • Removes the unnecessary postcss-import dependency and Mix configuration.

@taylorotwell taylorotwell merged commit a643cbb into 2.x May 30, 2022
@taylorotwell taylorotwell deleted the tailwind-streamline branch May 30, 2022 13:18
@NicoHood
Copy link

I am wondering how would I get those fixes, if I already installed jetstream? They seem to be minor for sure, but let's say I want to be in sync with the latest version, isn't there a simple way to upgrade all my files?

@driesvints
Copy link
Member

You're going to have to do the changes manually as Jetstream is a scaffold tool.

@NicoHood
Copy link

NicoHood commented Jun 2, 2022

That's a pitty. Isnt there a way to at least document those changes? Or is there a way to reinstall and check the changes via git and undo them, if the file was changed by myself (which is very unlikely). How can I ensure, that I don't miss critical updates?

@satoved
Copy link

satoved commented Jun 25, 2022

@NicoHood There are no critical updates, until you need a new feature.

It will continue working as it is in your project.

Generally, I tend to look over all releases of Jetstream with code diffs, and I take what I like.

E.g. one cool undocumented feature was 2FA confirmation.

@NicoHood
Copy link

Could this method be at least documented somewhere? I guess you will do a diff any only take code from a special skeleton folder that is usually copied when installing. I understand that this is a manual process, but documenting this would help a lot.

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.

None yet

5 participants