# fluttersdk_wind is now wind_kit: new names for the FlutterSDK packages and how to migrate

> The FlutterSDK packages now live under my own name: fluttersdk_wind is wind_kit, fluttersdk_dusk is tapir, fluttersdk_telescope is crumbs and fluttersdk_artisan is dowel, all at 1.x on pub.dev. The old names are discontinued. Swap the dependency and the import; a Wind app also moves its Material import to material_ui.

- Published: 2026-11-18
- Reading time: 6 min
- Tags: flutter, dart, wind-kit, tapir, crumbs, dowel, magic, open-source
- Language: en
- Canonical URL: https://anilcancakir.com/blog/fluttersdk-packages-renamed
- Translation (tr): [fluttersdk_wind artık wind_kit: FlutterSDK paketlerinin yeni adları ve geçiş rehberi](https://anilcancakir.com/tr/blog/fluttersdk-packages-renamed.md)

Today, I'll tell you where my FlutterSDK packages went and how to move your app over. If you run `flutter pub get` on a project that still uses one of them, you have probably seen this line already:

```text
fluttersdk_wind 1.11.2 (discontinued replaced by wind_kit)
```

That is the whole story in one line. Every package kept its code, got a new name, and moved under my own name: the GitHub repositories live at `github.com/anilcancakir`, the packages sit under the `anilcancakir.com` publisher on pub.dev, and the docs live on this site. The old names get no more releases.

What you'll walk away with:

- the new name of every package
- why the names changed, and why they carry my name and not a new brand
- the migration of a real Wind app, run on Flutter 3.50
- what the move costs, honestly

Let's start.

## The short version

| Was | Is | Latest |
|:---|:---|:---|
| `fluttersdk_wind` | [`wind_kit`](https://anilcancakir.com/wind_kit) | 1.12.2 |
| `fluttersdk_wind_diagnostics_contracts` | `wind_kit_diagnostics_contracts` | 1.3.0 |
| `fluttersdk_dusk` | [`tapir`](https://anilcancakir.com/tapir) | 1.1.0 |
| `fluttersdk_telescope` | [`crumbs`](https://anilcancakir.com/crumbs) | 1.1.1 |
| `fluttersdk_artisan` and `magic_cli` | [`dowel`](https://anilcancakir.com/dowel) | 1.1.0 |
| `magic` and its plugins | [`magic`](https://anilcancakir.com/magic), same names | 1.1.0 (core) |
| `fluttersdk/magic-starter-laravel` (Packagist) | `anilcancakir/magic-starter-laravel` | 1.0.3 |

On pub.dev every old package is marked discontinued and points at its new name, so the `pub get` warning above tells you where to go.

## Why the names changed

Flutter is a trademark of Google. Google asked me to take FLUTTER out of the name of my brand, my packages and my profiles, and I agreed. That is fair: a brand called FlutterSDK reads like the official SDK, and it isn't one. What stays allowed is describing compatibility, so a package can still say it is "for Flutter". That's how every page here talks about them now.

So the names had to go, and the code did not. The rename itself changed no behaviour; the releases around it did a few other things, and the migration below covers them.

## Why my own name, not a new brand

I could have picked a new umbrella name. I went the other way: the site, the publisher and the repositories all carry my name. Two of the best known Flutter packages do the same, `felangel/bloc` and `rrousselGit/riverpod` both live on personal GitHub accounts. A brand is one more thing to explain, rename and defend. My name is already on the code.

There is also a practical reason. On pub.dev a package name is forever, but the publisher can move later. So I put the permanent choices into the package names and kept the movable one personal. The names follow four rules:

- No Google marks: no flutter, no dart, no firebase.
- No Laravel product names. Dusk, Telescope and Artisan were Laravel names, so they went too.
- English, short, and saying the job.
- No brand prefix, so a name does not depend on a brand.

That gave `tapir` (an agent taps through your app), `crumbs` (the trail of logs, requests and errors your agent reads) and `dowel` (the small pin under every plugin, holding the CLI together). `wind_kit` kept Wind, since the bare `wind` is taken on pub.dev.

## Move a Wind app

Wind has the most users, so let's look at it first. I made a small app on `fluttersdk_wind` 1.11.2 and moved it to `wind_kit`. Three things change: the package, the import, and the Material import.

Swap the package:

```bash
flutter pub remove fluttersdk_wind
flutter pub add wind_kit material_ui
```

Replace the import in your code:

```bash
grep -rl 'package:fluttersdk_wind/' lib test | xargs sed -i.bak 's#package:fluttersdk_wind/fluttersdk_wind.dart#package:wind_kit/wind_kit.dart#'
find lib test -name '*.bak' -delete
```

`wind_kit` builds on `material_ui`, the package that replaces `package:flutter/material.dart` (Flutter 3.50 deprecates the old barrel). Your `MaterialApp`, `ThemeData` and `Colors` must come from the same place as Wind's, or you get "No MaterialLocalizations found" at run time. One fix moves the imports for you:

```bash
dart fix --apply --code=migrate_design_widgets
```

That's all for my app. The top of `main.dart` now reads:

```dart
import 'package:material_ui/material_ui.dart';
import 'package:wind_kit/wind_kit.dart';
```

No `W*` or `Wind*` class changed, and every className behaves as before. `dart analyze` says `No issues found!`, and `flutter pub deps` lists no `fluttersdk` package. Let's give it a shot:

![Four dark rows, each with an old fluttersdk package name struck through on the left and its new name in blue on the right](https://cdn.kodizm.com/t/anilcancakir/blog/1a51776ebfd0b8a2-960x340.png "The test app after the move, built with wind_kit 1.12.2")

> [!WARNING]
> Do not keep both packages in one app. Each has its own `WindTheme`, so a `WDiv` from one finds no theme from the other. If a dependency of yours still pulls `fluttersdk_wind`, update it first.

`wind_kit` needs Dart 3.13 and Flutter 3.47. An app on an older SDK stays on `fluttersdk_wind` 1.11.x for now. The [upgrade guide](https://anilcancakir.com/wind_kit/docs/getting-started/upgrade-guide) covers the rest, including the `flutter_localizations` delegates.

## tapir, crumbs and dowel

These three rename more than the package, because their names were everywhere: classes, CLI commands, MCP tools, environment variables. The pattern is the same for each:

- `Dusk*` classes are `Tapir*`, `dusk:*` commands are `tapir:*`, `dusk_*` MCP tools are `tapir_*`.
- `Telescope*` classes are `Crumbs*`, `telescope:*` is `crumbs:*`, `TELESCOPE_DISABLE` is `CRUMBS_DISABLE`.
- `Artisan*` classes are `Dowel*`, `bin/fsa` is `bin/dowel`, `.artisan/` is `.dowel/`, and the `fluttersdk` server in `.mcp.json` is now `dowel`.

Nothing is migrated automatically, so follow the guides in order: [dowel first](https://anilcancakir.com/dowel/docs/getting-started/migrating-from-fluttersdk-artisan), then [tapir](https://anilcancakir.com/tapir/docs/getting-started/migrating-from-fluttersdk-dusk). The crumbs rename is listed in its [changelog](https://pub.dev/packages/crumbs/changelog). After the move, reconnect your MCP client, and rename any saved `dusk_*` tool names in an allow list or a prompt.

## Magic apps

Magic kept its name, so the package line does not change, but Magic 1.0 moved onto the renamed packages. It depends on `wind_kit` and `dowel`, and the CLI command changed with it:

```bash
# Before
dart run magic:artisan make:controller Todo

# After
dart run magic:dowel make:controller Todo
```

If your backend uses the Laravel starter, the Composer package is `anilcancakir/magic-starter-laravel` and the PHP namespace is `AnilcanCakir\MagicStarter\`. The road from Magic 0.0.x to 1.x has more breaking changes than the rename, so read the [changelog](https://pub.dev/packages/magic/changelog) before you bump it.

## What else moved

- **Repositories.** All of them moved to [github.com/anilcancakir](https://github.com/anilcancakir) with their stars, issues and history. GitHub redirects the old URLs for now, but update your links: the redirects end when the old organisation goes away.
- **Docs.** Every package has its page and docs on this site, at `anilcancakir.com/<package>`. Old fluttersdk.com links redirect here for now.
- **AI skills.** `npx skills add anilcancakir/ai` installs the skills for Claude Code, Cursor and the others.
- **MCP.** tapir, crumbs and dowel are in the MCP registry as `io.github.anilcancakir/<name>`, and the docs MCP server is `https://mcp.anilcancakir.com`.

## What it costs

A rename is not free, and I'd rather say it plainly.

The numbers start from zero. On the day I write this, `fluttersdk_wind` has 32 likes and 81,959 downloads in the last 30 days, and `wind_kit` has 2 likes and 326. Those 82 thousand installs run a package that gets no more feature releases. If one of them is yours, the move above takes a few minutes.

Old links break later, not now. Redirects cover the old repositories and the old site today, but not forever. A README, a blog post or a bookmark that points at `fluttersdk` will stop working at some point.

And the SDK floor moved. `wind_kit` needs Flutter 3.47, so an older app has to upgrade Flutter first or stay behind.

## Try it

```bash
flutter pub add wind_kit material_ui
```

The packages are on [anilcancakir.com](https://anilcancakir.com): [Wind](https://anilcancakir.com/wind_kit), [Magic](https://anilcancakir.com/magic), [tapir](https://anilcancakir.com/tapir), [crumbs](https://anilcancakir.com/crumbs) and [dowel](https://anilcancakir.com/dowel). Same code, new names.

That's all. Have a nice day.
