Amicons 1.0 alpha 12

[Studio384]

Amicons 1.0 alpha 12 is a major release. This update contains a few updated icons and some new icons. The primary focus however is on major improvements to our development pipeline, documentation and release systems.

Icons

New icons

• book-bookmark

Updated icons

We've included a number of brand icon updates. Especially the GitHub logo is finally up-to-date after missing out on the logo redesign from 2015.

We've also updated a couple of minor icons. A larger refresh of our icon set, including better defined design guidelines, will follow with alpha 13.

• 8dd10d4 Various brand updates
  • facebook-messenger now matches its 2025 redesign.
  • github now matches its 2026 redesign.
  • google-play now matches its 2022 redesign.
  • visual-studio now matches the Visual Studio 2026 logo.
• 846f723 book has been updated with wider pages and updated border radii.
• 519162c bug has gained some weight, and attached its legs elsewhere.
• 3c4cec5 compress and expand have been updated with less aggressive border radii.

React component

• 13f28e7 Removes our dependency on html-react-parser. This eliminates 12 additional indirect dependencies.
• c6d01a4 Removes our dependency on clsx, which eliminats our last dependency.
• 6337cb4 rotate property can now be any numeric value, and is no longer limited to 0, 90, 180, 270, and false.
• 7a7981e When no icon is set to the component or the icon is invalid, the component will now render aiCircleQuestion by default, with the fade animation enabled.
• a1f83c1 Implements Oxc for linting and formatting.

Bugfixes

• 6337cb4 Fixes incorrect prefixes in the Amicon component.
• 2720463 Fixes a bug where rotate classes could be missing.

Documentation

• 4b32fc5 Playground options can now wrap, especially for playground settings with many options.
• 7558a14 Removes icons that were listed twice.
• 70b6500 Major improvements to how our Release component works in the documentation.
• 9167679 Bump year in the footer. We were running 2 years behind...
• 52b2c3d Adds the missing "Connectivity" category.
• c074271 e147b1e 96ca16c Various improvements to icon categories and tags.
• 14cdb03 When a category has no icons in the current filter, instead of disappearing it now becomes translucent.
• 01a3771 Changelogs can now show items related to the documentation.
• 9181305 d4e314b 9002bbc c930e88 95a4e43 50b3f2c 1b29426 35760a8 e1005b3 0741ff0 3621bc1 b9ca430 d2df8bf 8e626cf 02571f1 d9b8075 aa6d319 1604f86 02c14b3 e730501 414516c 480581f 1f84514 c738213 d27ad51 7d81365 bce9154 14a42e4 8b1af93 27156aa 1cf3761 08439a9 Major documentation redesign based on Tailwind and Base UI rather than Joy UI.
• 2a5c2be f5b41ca Improved search performance, icons that match on tags are now also returned.

Bugfixes

• aff5192 Fixes an issue where the React Compiler wasn't being used for the documentation.
• ba0f7b1 17bfabf Fixes various typos in the documentation.
• a813fdb Fixes the missing debounce documentation in the sidebar.
• 88cd3de Fixes the documentation example naming icons incorrectly.
• fde36d9 Fixes buggy behavior when searching for icons by properly debouncing input.

Tooling

• 61b9045 Replaces basic tsc with tsup.
• 5084e43 Optimizes the library generation.
• eb5db0a Bump our compilation target from es2020 to es2021.
• d4050a7 Add tailwind class functions to our configuration.
• 72255e1 8a9f578 c3c308c Migrate from npm to pnpm.
• c87c813 Fixes a bug where the rollup-plugin-visualizer wasn't in our dependencies.
• ba17352 Implement new linting with Oxc, replacing ESLint and Prettier.
• 73955a5 Update our deploy actions.
• 6651ab7 Add formatting and linting steps to deploy.
• 5781950 472f58b Add scripts to automate releases on GitHub and npm.

Bugfixes

• dae85b9 Fixes a bug where the CLI would report the completion of generating markdown before it actually happened.

Release strategy

Starting with alpha 12, we'll be changing our release strategy. We've been a bit all over the place, now we're codifying it. Every future 1.0 preview will, from here on out, be published as the latest release both on GitHub and npm.

Once 1.0 goes stable, the latest tag on npm will of course only serve stable future releases like 1.0.1, 1.1.0, and 2.0.0. Future previews like 1.1.0-alpha.1 will then be released only on next.

This also means that the current previews will now be in the main branch. Development on future previews happen in a branch like 1-alpha. This work will be merged into main, which will then trigger a release. This means that the current 1.0 branch will be removed. After the 1.0 release, main will of course always have the current stable release, and future preview versions can be found in next, with development branches merging into next, which then on its turn will merge into main when it reaches a stable release.