Migrating from @aquienpz

nitida was previously published as @aquienpz/*. If you are starting fresh, skip this page — nothing here affects you.

What changed

before	now
@aquienpz/sdk	@nitida/sdk
@aquienpz/asset-client	@nitida/asset-client
@aquienpz/asset-compressor-web	@nitida/asset-compressor-web
@aquienpz/asset-compressor-native	@nitida/asset-compressor-native
AquienpzClient	NitidaClient
AquienpzClientOptions	NitidaClientOptions
AquienpzProvider	NitidaProvider
useAquienpzClient	useNitidaClient

Nothing else. Same methods, same signatures, same behaviour, same CDN, same URLs, same keys. Assets uploaded under the old package are the same assets — the SHA did not change, so neither did a single URL.

The migration

bun remove @aquienpz/sdk @aquienpz/asset-client
bun add @nitida/sdk @nitida/asset-client

Then a find-and-replace over your source:

# imports
grep -rl '@aquienpz/' src | xargs sed -i '' 's|@aquienpz/|@nitida/|g'
# identifiers
grep -rl 'Aquienpz' src | xargs sed -i '' \
  -e 's/AquienpzClientOptions/NitidaClientOptions/g' \
  -e 's/AquienpzProvider/NitidaProvider/g' \
  -e 's/useAquienpzClient/useNitidaClient/g' \
  -e 's/AquienpzClient/NitidaClient/g'

Check your .md and .mdx too

We did this migration on our own repo and the script missed .mdx, because the extension list did not include it. Type-check was green, the build was green, and the three most-read pages of this very site still said @aquienpz/sdk.

A rename verified only by the compiler is verified halfway. The compiler sees imports; a brand name lives in prose.

Your version pins map one-to-one — @nitida/sdk@0.20.1 is the same code as @aquienpz/sdk@0.20.0, published under the new name.

Why there are no compatibility aliases

The new packages do not export AquienpzClient as a deprecated alias, and that is on purpose.

@nitida/sdk is a new package. Nobody has ever written AquienpzClient against it, so an alias would not be preserving compatibility — it would be importing legacy into an API that never had any, and every reader of the reference would meet a deprecated name on day one.

Compatibility is preserved where it actually exists: the old packages are still published and still resolve. Anything pinned to @aquienpz/* keeps working, indefinitely, exactly as it did.

What the old packages do and do not get

still installable	✅ forever. Nothing was unpublished
still works	✅ same API, same CDN, same assets
gets new features	❌ the repository is now the source of @nitida/*
gets bug fixes	❌ same reason

So there is no deadline and no breakage — but a project left on the old name stops receiving fixes. Migrate when it suits you; the change is mechanical.

Things that did NOT get renamed

Deliberately:

• The CDN host (8ok.uk). Renaming it would break URLs stored in five tenants’ databases. A short opaque delivery host is normal — imgix and Cloudinary do the same.
• Your tenant code, and every key you already hold.
• The API endpoint you were already given. The branded api.nitida.gofuture.space is an additional name for the same service; an older address you hold keeps working — see Credentials.