Extensions not loading

[naskio]

Hello,
I am not able to load extensions to Directus v9.6.0.
I have an extension called 'example' in extensions/endpoints/example/index.js

"use strict";module.exports=e=>{e.get("/",((e,l)=>l.send("Hello, World!")))};

GET /example return this error

{"errors":[{"message":"Route /example doesn't exist.","extensions":{"code":"ROUTE_NOT_FOUND"}}]}

I am currently using Docker (+ C ompose) with a mounted volume:

Am I missing something ?
Thanks for your help.

[rijkvanzanten]

Odd! I think it's how the extension is loaded into the docker container, rather than the extension itself. I just copy pasted your code into my extensions folder, and it works as expected:

[naskio]

Hey
Thanks for your answer
Maybe there is a difference when in production mode (public url is set in my case).
I also checked if the folder exists inside the container and it is the case.
I will try to setup a local environment and test it.

[rijkvanzanten]

@naskio One quick way to make sure Directus is at least aware of your endpoint is by keeping an eye on stdout. It will log ✨ Loaded extensions: example if Directus detected the extensions folder 👍🏻

[naskio]

Indeed, After trying to load them locally everything worked as expected:

In prod, I kept getting this warning:

After investigating it, I found out that the extension-folders (interfaces, layouts, modules, ...) need to exist to be able to load the extensions.

After creating the extension-folders, the extensions has been detected normally:

[azrikahar]

Nice catch! Seems like it's the same "friction" faced in #9955 (reply in thread). cc @nickrum

[staminna]

I have 4 different extensions loaded and I can see the lightning start emoji but none of them is actually changing anything in Directus.
Is there a menu I should click on a box inside the admin UI?

[br41nslug]

What kind of extensions @staminna ? Only the module type should directly change anything and might need to be enabled/shown under Project Settings > Modules.

[staminna]

@br41nslug I found out! It was on the display's link of the fields options! Thanks!

[dfanica]

Just to update this thread in case someone else stumbles across it... I was having a similar issue recently and it turns out the folder endpoints is no longer being used (or the syntax has changed and there's no documentation on this).

You now need to create a folder directus-extension-{name} and have the a package.json file with some required keys. I will link the documentation here: https://docs.directus.io/guides/extensions/endpoints-api-proxy-twilio.html

.env variables are will not work via process.env anymore, you now need to load it via the handler:

handler: (router, { services, env, logger }) => { ... }

I hope this helps someone. I was going mad after updating directus trying to figure out why my custom endpoints are not loading anymore.

P.S. If you're having issues with the package.json file you can always create an extension of type endpoint via npm init directus-extension; just make sure to remove the "type" : "module" from it afterwords as it doesn't like that apparently.

[br41nslug]

I was having a similar issue recently and it turns out the folder endpoints is no longer being used

https://docs.directus.io/releases/breaking-changes.html#deprecated-typed-extension-folders