Error message after importing terms with TM last update

Same here. Had uninstalled TM when it didn't work any more, reinstalled today on D 10.3.5 together with fancytree/fancytree - but it doesn't show any terms in any of my 10 or 15 existing groups, instead I see this error message (although it poses just as a warning):

Warning: file_get_contents(libraries/jquery.fancytree/dist/jquery.fancytree.min.js): Failed to open stream: No such file or directory in _locale_parse_js_file() (line 1097 of core/modules/locale/locale.module).

_locale_parse_js_file('libraries/jquery.fancytree/dist/jquery.fancytree.min.js') (Line: 529)
locale_js_translate(Array, Object) (Line: 485)
locale_js_alter(Array, Object, Object) (Line: 552)
Drupal\Core\Extension\ModuleHandler->alter('js', Array, Object, Object) (Line: 313)
Drupal\Core\Asset\AssetResolver->getJsAssets(Object, , Object) (Line: 330)
Drupal\Core\Render\HtmlResponseAttachmentsProcessor->processAssetLibraries(Object, Array) (Line: 167)
Drupal\Core\Render\HtmlResponseAttachmentsProcessor->processAttachments(Object) (Line: 97)
Drupal\big_pipe\Render\BigPipeResponseAttachmentsProcessor->processAttachments(Object) (Line: 45)
Drupal\Core\EventSubscriber\HtmlResponseSubscriber->onRespond(Object, 'kernel.response', Object)
call_user_func(Array, Object, 'kernel.response', Object) (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.response') (Line: 214)
Symfony\Component\HttpKernel\HttpKernel->filterResponse(Object, Object, 1) (Line: 202)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 53)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle(Object, 1, 1) (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 50)
Drupal\ban\BanMiddleware->handle(Object, 1, 1) (Line: 263)
Drupal\shield\ShieldMiddleware->bypass(Object, 1, 1) (Line: 219)
Drupal\shield\ShieldMiddleware->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 741)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

I would imagine thats because of this: https://www.drupal.org/project/taxonomy_manager/issues/3449481 📌 Install jquery.fancytree via Composer instead of CDN Fixed

If you rerun composer require 'drupal/taxonomy_manager:^2.0' does that solve the issue? (Assuming you're using Composer)

Thanks, but no. Then did drush un taxonomy_manager, composer remove, reinstalled, same result.

@aaron.ferris @dgwolf
Tried to install TM again by composer on several from scratch Drupal >10.x release and issue is always the same.
By the moment i solved installing TM older 2.0.12 version with composer require 'drupal/taxonomy_manager:<2.0.13' which run fine for my needs with jquery.ui library only

Hmm, id need to refamiliarise myself with including libraries via composer, but you could try to get around it by pulling the fancy tree library down and including it in the relevant place.

/libraries/jquery.fancytree/dist/skin-lion/ui.fancytree.min.css
/libraries/jquery.fancytree/dist/jquery.fancytree.min.js

The library: https://github.com/mar10/fancytree/archive/refs/tags/v2.37.0.zip

Thanks, I will try your suggestion.
In the meantime, looking for how to install third-party libraries via Composer I came across this solution for the Varbase theme → which seems to have the same problem with fancy.tree library. It requires NPM and the installation of the composer-installers-extender plugin.
I can't apply it because the composer provided by the host can only be used and not configured|modified, but for those with full tools control it seems like a good solution.
One question as a Composer novice: To your knowledge, are those instructions permanent or temporary for a specific use? And if they are permanent, does it change the main operation of Composer in any way?
Thanks again

@aaron.ferris [Solved] In fact, your suggestion worked perfectly, unlike what I would have thought. In this case, the legacy method prevailed. Not that the library adds much (I would have preferred without it, but that's my personal taste), but importantly, the latest Taxonomy Manager release is now working fine.
Thank you!

No problem, glad you got it sorted for now.

Thanks @
We are working on the better solution in here: ✨ Change require custom libraries to suggestions as a better method with more options Needs work
I will close the issue as it looks like it was solved.

Thanks to you @vladimiraus