Skip to content

v2.0.0 — The package is now @comwit/state

Choose a tag to compare

View all tags
@Moon-DaeSeung Moon-DaeSeung released this 03 Jul 10:53
· 4 commits to main since this release
v2.0.0
e630351

The package is now @comwit/state

comwit is now published on npm as @comwit/state. That's the whole change — there are no API changes, no renamed exports, no behavioral differences. Only two things move:

  1. The package you install: comwit → @comwit/state
  2. The specifier you import from: from 'comwit' → from '@comwit/state'

The ComwitProvider component, the library.comwit.io docs, and this GitHub repo keep their names. Only the npm package identifier changed.

Migration

For most projects this is a two-line change:

yarn remove comwit
yarn add @comwit/state
- import { model, action, query, ComwitProvider } from 'comwit'
+ import { model, action, query, ComwitProvider } from '@comwit/state'

A project-wide find-and-replace of from 'comwit' → from '@comwit/state' is safe — the export surface is identical.

You don't have to migrate immediately

We took the soft path — nothing breaks on upgrade:

  • comwit@2.0.0 was published as a thin compatibility shim that simply re-exports @comwit/state. Existing import ... from 'comwit' code keeps working unchanged.
  • The comwit package is now deprecated on npm with a notice pointing to @comwit/state.

New projects should install @comwit/state directly; existing projects can migrate whenever convenient. The shim is a bridge, not a long-term home.

Why a major version?

The public API is unchanged, but renaming the package is breaking for consumers (install name + import path move), so this ships as 2.0.0. Both @comwit/state and the comwit compatibility shim are published at 2.0.0 and track the same version line going forward.

Links

🤖 Generated with Claude Code

Assets 2
Loading