Skip to content

Cake5 - Next#19

Merged
passchn merged 13 commits intobrandcom:cake5-nextfrom
bor-attila:cake5-next
Jan 25, 2026
Merged

Cake5 - Next#19
passchn merged 13 commits intobrandcom:cake5-nextfrom
bor-attila:cake5-next

Conversation

@bor-attila
Copy link
Contributor

@bor-attila bor-attila commented Mar 21, 2024

I made some modifications, but I was not able to finish.

  • I removed the ConfigDefaults class and I used the Helper's default config method. (Helpers uses InstanceConfigTrait)
  • all config related to prod/dev removed, now you must use explicitly: Environment::PRODUCTION or Environment::DEVELOPMENT . For detector Environment::FROM_DETECTOR can be used. Not tested yet. lol
  • if production is set, and no manifest file - no more exception - but actually this should maybe optional (!?)
  • The Helper completly reworked
    Since the environment is explicitly defined the prodFilter and devFiles is unnecessary
    You can add files (scripts/css) separetly to 'prod' or 'env' or 'both'
  • Updated README - still not complete yet
  • Updated examples file. exple: changed webroot_src to resources
  • Added render mode for 'lazy' rendering - disabled by default

TODO:

If you think is too much - feel free to modify and/or delete. Enjoy the bugs.

UPDATE1:

  • fixed CS
  • I removed the parallel option from composer cs-check because the plugin isn't large enough to warrant it. Additionally, for some reason, it's not working for me.

@bor-attila bor-attila marked this pull request as ready for review March 22, 2024 03:33
@tyler36
Copy link

tyler36 commented Aug 21, 2024

I'm interested in getting Vite/TailwindCSS intergrated into a CakePHP project.
Are you still working on this? What is the best way I can help test this?

@passchn
Copy link
Collaborator

passchn commented Aug 25, 2024

@tyler36 You can integrate vite and tailwind perfectly fine with the current version of this plugin. I am using tailwind myself. This PR is for a new major release to fix some design issues. I was however not taking the time to look into this for some reasons. If you have specific questions about integrating tailwind, you could open a new issue or DM me on the CakePHP Slack.

@LordSimal
Copy link

there is also https://github.com/cakephp/app-tailwind for a basic tailwind setup but without this plugin.

@LordSimal
Copy link

LordSimal commented Jan 23, 2026

@bor-attila FYI: This plugin seems to be pretty much abandoned as the main developer does not work at brandcom any more and brandcom themselves don't answer to my email's.

I'd recommend you swtich to https://github.com/josbeir/cakephp-vite as that is maintained, has more features and is Cake 5.3 ready

@passchn
Copy link
Collaborator

passchn commented Jan 24, 2026

Hi, as @LordSimal says, here is not much action happening anymore. I use the plugin myself in two personal projects, but don't have the time to keep everything up to date with the most recent vite versions all the time.

If the suggested plugin is a good alternative, I am happy for that.

Otherwise we can try to find a new organization for this plugin. The issues seems to be the licensing which prevents open sourcing/forking. I can ask around at brandcom as well.

For individuals, I see no problem in just creating a fork and adapt it as needed. Every frontend setup is different so it is hard to make it suitable for every use case anyways.

@bor-attila
Copy link
Contributor Author

I just had a few minutes, so I tried to make it compatible with 5.3 since I still use this repo for some older projects.

If they merge or use my PR, that’s fine; if not, that’s fine too. I did it for free. :-)

I’m happy to see that other plugins are being maintained, but in Awesome Vite this plugin is still recommended.

Anyway, I’ll take a look at the other plugin as well. Thx for the info.

@passchn passchn changed the base branch from cake5 to cake5-next January 25, 2026 17:05
@passchn passchn merged commit e40dd36 into brandcom:cake5-next Jan 25, 2026
0 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants