Hey dear friends! 
Weāve implemented basic accessibility 
across all our components!
You can now access it in version 0.0.5-alpha.12. 
Plus, weāve squashed a lot of bugs! 
Please help us to test before releasing! 
{:mishka_chelekom, "~> 0.0.5-alpha.12", only: :dev}
mix mishka.ui.gen.components --import --helpers --global
Hey Elixir friends, This is a Huge Update !! 
Excited to announce Mishka Chelekom v0.0.5 is out! 5 new components, improved custom classes support, and accessibility across all components.
Support the project please
{:mishka_chelekom, "~> 0.0.5", only: :dev}
mix mishka.ui.gen.components --import --helpers --global
Next version of Mishka Chelekom with support for dynamic design system (including daisyUI) will start from next week and this version might take a bit longer. Weāre trying to convert all the currently hard-coded sections into Tailwind configs and CSS variables! 
Not sure if anyone asked this before, but is there also a standard way (i.e. a dependency āhassleā based one) to use the components (instead of letting the installer do it automatically)?
Thanks
Hello dear friend. Iām not entirely sure I understand your question. If my explanation doesnāt fully address your issue, please provide more details or an example.
Generally, there are several ways to install components, as mentioned in our documentation:
Install each component separately:
mix mishka.ui.gen.component alert
Limiting a specific component, for example:
mix mishka.ui.gen.component alert --color info --variant default
# For Windows users please use `""` when you have more than
# one value for an argument
mix mishka.ui.gen.component alert --color "info,danger"
If you want to install all components with helpers macro (easy import):
mix mishka.ui.gen.components --import --yes
# Or you want to install helpers too
mix mishka.ui.gen.components --import --helpers --yes
If you want the CLI to do everything for you without needing anything else, simply run:
mix mishka.ui.gen.components --import --helpers --global --yes
This will even handle the replacement process with Phoenix components for you. The last method, installation with a single command, is my personal recommendation if you want to use all of our components.
Thank you in advance
What I am asking is whether thereās a way to use the components without running the generators, i.e. simply add a certain dependency or dependencies to the web app in the project?
Thanks
Iām sorry, I just realized. For now unfortunately No,
Our entire approach is based on CLI so that you can install whatever you need and easily customize it.
I think this is one of the features of this library makes it specific.
The quick and easy way is for you to create a project, put all the components in it, and install it. This is a temporary solution.
I will try to add an installable package to the project in future versions so that you wonāt need the CLI.
I think this will be added in a few more versions. 
Thank you.
A first draft of mix assets has been added to the Mishka Chelekom project using igniter and the bun library in elixirā our first step toward bigger components like an editor.
Try out version 0.0.6-alpha.2 and use:
{:mishka_chelekom, "~> 0.0.6-alpha.2", only: :dev}
# install
mix mishka.assets.deps axios
mix mishka.assets.deps axios,lodash
# uninstall
mix mishka.assets.deps axios --remove
mix mishka.assets.deps axios,lodash --remove
If you have any of npm, yarn, or bun installed, the system will automatically use the first available one in that orderāunless you specify otherwise. To choose a specific package manager, use an option like:
mix mishka.assets.deps axios --npm --yes
Note: You must also specify the package manager when removing a dependency.
If none of the three are available, bun will be used by default, and its binary will be placed in your build folder.
Road to add bigger components 
Mishka Chelekom just passed 10K downloads 
ā and itās only used in dev, not in prod! Hope elixir community support us more .
The next release will be our biggest yet, packed with optimizations.
Itāll take time, but itās worth the wait. 
Hi my friends, it is not out long term update for Mishka Chelekom but this version fixes Phoenix 1.8 errors.
We still working on our next version that will be our biggest one 
{:mishka_chelekom, "~> 0.0.7", only: :dev}
Weāre excited to share that our library has been downloaded over 15,000 times on Hex.pm! 
Thank you so much for your trust and support! 
Hereās some great news:
After months of trial and error, we finally opened a pull request in the Mishka Chelekom project!
Weāve been working super hard to reach the next version, and you can check out the progress at the link below.
These days, weāre working full-time to bring the new release to life! 
Itās also worth mentioning that Tailwind v4 brought major changes, which unfortunately broke a lot of components 
. Fixing this has taken a huge amount of effort on its own!
But hereās the good part:
With this new version, you no longer need to dig into each component just to change colors.
Weāve moved all the colors into a CSS file, and the CLI now builds it for you effortlessly.
Please consider supporting the project so we can cover the costs and keep moving forward. 
Hello friends,
Yesterday, I released the first beta version. Due to the large number of changes, I really need your help with testing.
I hope youāll support us by trying out the new version.
The minimum requirements are Tailwind 4 and Phoenix 1.8.
{:mishka_chelekom, "~> 0.0.8-beta.1", only: :dev}
For creating components
mix mishka.ui.gen.components --import --helpers --global
# OR
mix mishka.ui.gen.components --import --helpers --global --yes
By the way it creates priv/mishka_chelekom/config.exs for you and you can change the colors or another stuff! and run top command or if it is just about color just run this.
mix mishka.ui.css.config --regenerate
If you need create this config and change it, after that run the mishka.ui.gen.components
Please after install deps run
Initialize a configuration file:
mix mishka.ui.css.config --init
Force overwrite existing configuration with sample:
mix mishka.ui.css.config --init --force
Weāre almost in the final stages of the release, and unless any major issues come up, I believe weāll reach the new version within the next 3 to 4 days.
I hope we can count on your support with testing during this time.
Thank you in advance
Hey 
Beta v2 was released yesterday!
Weāve almost completed a full revamp of all our components
Next, weāll be focusing on addressing user-reported issues 
Huge thanks in advance for your support in testing the beta versions 
{:mishka_chelekom, "~> 0.0.8-beta.2", only: :dev}
We are absolutely thrilled to announce the release of version 0.0.8 of Mishka Chelekom! Hits 16K+ Downloads
This release represents over 21K lines of code changes across our components
Key Highlights of v0.0.8:
Complete Tailwind 4 Migration: All components now leverage the latest Tailwind CSS capabilities
Phoenix 1.8 Optimization: Full compatibility and performance improvements for the latest Phoenix release
Custom Configuration System: No more manual color adjustments in generated code! Our new config file system enables you to:
Generate all components with your custom color palette
Implement your own CSS styling (which were defined in this lib components)
Achieve complete component customization with ease
New components and JsHooks: This version has some new components and Infrastructure JsHooks
Support Open Source Development This free and open-source project thrives with community support. If you find value in our work, please consider sponsoring us, even a coffee-sized contribution makes a difference! 
Please for more information, read this Blog Post:
Would it automatically remove all Tailwind stuff in the generated code?
Hi dear Eiji,
In this version, weāve moved all color-related styles outside of the components and provided them as examples. The result is a file called mishka_chelekom.css, which is located in the vendor directory of your project. Weāve also added it as an import in app.css.
Every line in that file ā which currently contains only color definitions ā can be overridden via the config file located in the priv directory.
You can see it in action in the video below:
https://www.youtube.com/watch?v=kVRgVgD9xZ4
The only important point to mention here is that we completely replace the @theme in app.css with our own version.
If you had previously made hardcoded changes to the components, I think those changes might be overwritten. So, itās a good idea to take a backup beforehand.
If I didnāt fully understand your question, please explain it to me with an example. If the feature youāre referring to doesnāt exist, Iāll definitely consider implementing it in the next release.
Overall, our components are simple .eex files that can be customized using several parameters like color, size, border, and so on.
In previous versions, you could only choose between predefined options. But now, in addition to that, you can completely override any color using the config file.
In new version we will try to move shadow size and etc to config file too
For example, we define these and use it inside html tailwind!
:root {
--opacity-base: 10;
--overlay-opacity: 100%;
Simply you use naming like custom CSS which is often used here and on other forums to refer user-defined CSS usually for the entire site as an alternative to using Tailwind, Bootstrap and any other CSS library/framework. This is a bit confusing especially for developers who do not know anything about your project.
Yes you are right! I changed this to Implement your own CSS styling (which were defined in this lib components)
Thank you
If possible, Iād appreciate your help with sharing the post on social media.
Reddit: https://www.reddit.com/r/elixir/comments/1ntdjks/mishka_chelekom_hits_16k_downloads_free/
X(twitter): https://x.com/shahryar_tbiz/status/1972586057943412952
Dear friends and colleagues,
What features do you think should be added to the CLI for the Mishka Chelekom project?
Weād greatly appreciate your suggestions, especially for potential Mix tasks that could enhance the project.
Thank you in advance!
Ā© Copyright Elixir Forum | Terms | Privacy & Cookies
