What happen when we changed our NPM scope?

[setoelkahfi]

I should've asked this before doing the migration, but is it simply updating the agent.json file? We recently moved our NPM distribtuion organization scope from smbcloud to getsigit.

siGit Code on NPM.

I think I should've keep updating the older organization scope as well before opening the PR.

[MLuc24]

Updating agent.json is the mechanism, yes, but the migration is only half done — the field that actually matters for installation is still on the old scope. Line 47 reads

"package": "@smbcloud/sigit@1.5.2"

while repository, website and license_url have all moved to getsigit. Anyone installing through the registry today still gets the old package.

Three things the registry's validator will hold you to when you change it. It resolves the package against https://registry.npmjs.org/<name>, so @getsigit/sigit has to be published under the new scope before the PR can go green — a rename on your side alone is not enough. It rejects @latest, so the version stays pinned explicitly. And it checks that the version in the package string matches the top-level "version" field, currently 1.5.2, so those two have to move together whenever you bump.

Outside the registry, the old name does not stop working: @smbcloud/sigit keeps resolving for anyone who has it pinned or cached, and npm has no way to redirect it. npm deprecate @smbcloud/sigit "moved to @getsigit/sigit" is the usual way to leave a visible pointer, since the deprecation notice prints on install.

While you are in the file, "authors": ["smbCloud"] on line 9 is the other leftover — cosmetic, but it is the name people will see in the listing.

[setoelkahfi]

did you type all those em dashes?