Bundle extension loading but not working in 10.10.1

[boncossoftware]

Describe the Bug

My custom bundle extension seems to be loading and visible in the Settings -> Extensions tab (see image).

But they are not displayed in the collection item forms and are show up as "...not found" in the field interface settings (see image bellow).

Also, the endpoints and hooks don't seem to be working.

I have made sure my bundle meets all of the latests requirements explained here https://docs.directus.io/releases/breaking-changes.html#deprecated-typed-extension-folders. The bundle is currently being imported as a npm package (not placed in the extensions folder).

Also one more thing to note is that when I check the "/extensions/sources/index.js" being loading from the app it seems to be completely empty (see image).

To Reproduce

Wouldn't know exactly how to reproduce the issue with other extensions. I have a bundle type extension in typescript with many interfaces, endpoints, hooks and some displays and not sure if one of these is causing the issue. Might also be how the npm package is being build.

Directus Version

v10.10.1

Hosting Strategy

Self-Hosted (Custom)

[boncossoftware]

Forgot to mention that the bundle extension was working in version 10.9.3.

[br41nslug]

How are you installing/deploying Directus and its extensions? Did you update the extensions-sdk for your extension when updating the Directus instance?

[boncossoftware]

Yes, extensions-sdk version is currently at 11.0.1. I am deploying Directus in Google Cloud's App Engine and extension is added as a dependency in package.json. But haven't deployed this yet; the issue is occurring currently when I am running it locally on my machine.

[boncossoftware]

I can also see that the built app.js exports the interfaces, etc.

[wolfgang-hartl]

I am facing a similar Problem, with a slight difference. I've created a custom Hook inside of a bundle which works fine. But when adding an interface it doesn't show up. I've tried to add the interface with several ways:

1. through npm run add
2. manually
3. npx create-directus-extension@latest

I have registered the extensions inside of the package.json which are located at: ./extensions/homart/....

Directus is running locally with a docker-compose.yml file!

Directus Version 10.10.0 and 10.10.1 (both tested)
"@directus/extensions-sdk": "11.0.1",

When visiting the settings page only the hook shows up:

[KayhanB]

I experienced the same issue and found a workaround. When I deleted the records in the directus_extensions collection and restarted directus, the newly added extension started working. Make sure your bundle is packaged with the new extension before restarting. @wolfgang-hartl

[wolfgang-hartl]

I experienced the same issue and found a workaround. When I deleted the records in the directus_extensions collection and restarted directus, the newly added extension started working. Make sure your bundle is packaged with the new extension before restarting. @wolfgang-hartl

Thank you very much @KayhanB ... that works for me as well!! 👍

[boncossoftware]

Alright, I seem to have found the issue. It looks like there is an bug in the migration script "20240204A-marketplace.js" where it only migrates the resolved npm package as a module (in this case a bundle) but is not resolving the extensions contained in the bundle as a module type (see image bellow) but instead leaving the source as a "local".

This is the result in the database:

They should all be module types because they all come from the same bundle extension.

This causes an issue when building the entry points in "generateExtensionsEntrypoint" (found in node.js in the @directus/extensions package) because it is looking for a module source extension and, when it fails to do so, defaults to enabled being false (see image below).

[malipetek]

I experienced the same issue and found a workaround. When I deleted the records in the directus_extensions collection and restarted directus, the newly added extension started working. Make sure your bundle is packaged with the new extension before restarting. @wolfgang-hartl

Thanks, this was the case for my bundle extension as well. I guess this has something to do with starting with a faulty package.json

[aldoprogra]

I have hooks and endpoint working local but when deploying on railway they result to be enabled but they do no work. Should I build extensions when deploying? create a script that builds ? Thank you in advance

[wolfgang-hartl]

I have hooks and endpoint working local but when deploying on railway they result to be enabled but they do no work. Should I build extensions when deploying? create a script that builds ? Thank you in advance

Can only speak for myself, but deploying the extensions work fine for me. Make sure, that the dist folder is present when deploying your extensions. I guess it's also adviseable to change the version in the package.json in your extension if you modify an already deployed extension.

[aldoprogra]

I have hooks and endpoint working local but when deploying on railway they result to be enabled but they do no work. Should I build extensions when deploying? create a script that builds ? Thank you in advance

Can only speak for myself, but deploying the extensions work fine for me. Make sure, that the dist folder is present when deploying your extensions. I guess it's also adviseable to change the version in the package.json in your extension if you modify an already deployed extension.

Thank you very much! dist was in the .gitignore and removing it of course solved the problem. Thank you very much for the fast solution wolfgang!