Conversation
|
I'm interested in getting Vite/TailwindCSS intergrated into a CakePHP project. |
|
@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. |
|
there is also https://github.com/cakephp/app-tailwind for a basic tailwind setup but without this plugin. |
|
@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 |
|
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. |
|
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. |
I made some modifications, but I was not able to finish.
ConfigDefaultsclass and I used the Helper's default config method. (Helpers usesInstanceConfigTrait)Environment::PRODUCTIONorEnvironment::DEVELOPMENT. For detectorEnvironment::FROM_DETECTORcan be used. Not tested yet. lolSince the environment is explicitly defined the
prodFilteranddevFilesis unnecessaryYou can add files (scripts/css) separetly to 'prod' or 'env' or 'both'
webroot_srctoresourcesTODO:
If you think is too much - feel free to modify and/or delete. Enjoy the bugs.
UPDATE1: