Issue upgrading from v14.3.0 to 16.3.3 (Extension Manifest)

Questions
,
1

Hey all, I’m trying to upgrade my site from Umbraco version 14.3.0 to 16.3.3, using the Umbraco.CMS package in my ASP.NET project. However, I can’t figure out how to make the proper adjustments for the change that happended from version 14 to 15 (see [Breaking change]: Extension Manifest Type Architecture + Constants/Modal Tokens/Types moved to their package · Issue #22 · umbraco/Announcements · GitHub ). I get the following error:

TS2688: Build:Cannot find type definition file for ‘@umbraco-cms/backoffice/extension-types’.

Below is how my tsconfig.json file looks like

{
	"compilerOptions": {
		"lib": [ "es2021" ],
		"types": [ "@umbraco-cms/backoffice/extension-types" ]
	}
}

Is there something I’m missing? I’ve tried downloading extension-types but it seemingly won’t allow it as I already have the CMS package installed. I also haven’t been able to find any local files for umbraco-cms as I’m unsure where to look. And for reference, if I remove the “types“ line in tsconfig I get tons of errors regarding missing “@umbraco-cms/backoffice/localisation-api” that are fixed when I open any file containing errors, which I’m not sure if it has anything to do with this extention-types issue or not.

I have searched the web for a solution but the closest I’ve come is this thread that’s unfortunately missing the attachments ( Umbraco 15.1.2 Backoffice Typescript not detecting exports Umbraco #help-with-umbraco )

The above links both mention something about UmbExtensionManifest that I’m unsure of how I should change. Is that the only thing I need to do now? If so, should I change ManifestSection only, ManifestTypes only, or everything that begins with Manifest?

I’ve also tried upgrading to v15 as a stopgap before going to v16 but the issue persisted. I’m a bit lost on how to proceed from where I’m at, so any help is appreciated!

2

I suggest you create a new project using the umbraco dotnet template for an extension. That’ll show you a lot of configuration, like the ts configuration.

3

Thanks for the suggestion, I’ll give that a try.

4

Finally have an update on this. Turns out I somehow wasn’t properly updating the Umbraco.CMS package, for one reason or another. Fixed this by uninstalling the 14.3.0 Umbraco.CMS package and installing the newest version.

1 Like