Website news
Just a quick note to let you know that we have migrated our website to TailwindCSS 4 & DaisyUI 5. These were two big migrations that were on our todo-list, but we did not want to block a v4 release for. So now it’s been taken care of.
These kind of things are typically transparent for the user, but as you may know were have been experiencing issues with theming on the new site, and this is closely related to it.
The good news is that things are significantly better now. The bad news is that it’s not entirely 100% fixed either, so I’ve created and umbrella issue to track these styling issues.
One thing that has changed is that the theme toggle is now gone. Instead, the site will use whatever is configured in your operating system (so if you have it set to dark mode, it will use dark mode).
There’s also been a bunch of fixes big and small. I really need to give a shout-out to @jonathan_haas here who has been doing a ton of work sanding down the rough edges. Here’s a non-exhaustive list:
- Fixes to the seam allowance slider
- Remove broken links
- Fix issue with pattern export
- Fix a crash in the Editor inspect view, and other small inspect fixes
- Fixes in the measurements view of the Editor
- Improve performance in the core bezier reducer
- Translation fixes in various places
- Fix theming of the core SVG output
- Fix slider bug when entering the default value
- Bring back the public view of measurements sets
- Fix incorrect behaviour in Editor reset button
- Fix the deselection of included parts
All this and more is available on our website.
FreeSewing Studio
It’s been brought to my attention that I did a poor job at announcing the new Studio. Basically, I only mentioned it in the newsletter 
Which is kinda dumb of me because it’s a big change and a lot of work that went into v4 was to facilitate it.
So, the studio is our development environment that people can use to generate FreeSewing designs. In v3, this development environment only supported a single design.
Now in v4, our development environment not only ships with all FreeSewing designs on board, but you can add your own, and as many as you want.
In addition, it also integrates with the FreeSewing backend, so you do not only have access to all your measurements, you can also store your patterns in our backend, even from your custom designs.
You can try it yourself by running this:
npx @freesewing/studio
For people who like to work in our monorepo. You can not currently run a studio instance from the monorepo. But it is on my todo list to make this possible so you can enjoy the same benefits as people using the stand-along environment.
What more is coming?
The studio thing is a great reminder that I am not always great at telling people about the changes that we made. So I will try to be better at that. In particular, I plan to:
- Give an update 2 times per month (every 2 weeks more or less) of what’s going on (consider this the first one)
- Have a monthly release cycle for updating the packages we publish
In practical terms:
- We released v4 on April first and made a bunch of announcements
- I am now giving you an update of what’s been happening since
- Towards the 1st of May, we will look into bundling the work we did into a new release
That means that people who use FreeSewing as a library in their own projects will get all of that new stuff after a month or so. People who use our websites get is much sooner as we run the so-called bleeding edge of our own code 
Thank you to all contributors and everyone who helped us out by pointing out things that needed some love and care, we appreciate all of you 
