A lot of non-working extensions when upgrading from 11.8.0 to 11.12.0

Help
1

hi,

i’m trying to update directus from 11.8 to 11.12 but it seems a lot of extensions are no longer working including exts from directus-labs (for example experimental-m2a-interface)

is there any replacement or recommanded steps how to proceed?

Example of errors:

directus-development | file:///directus/node_modules/.pnpm/zod@4.0.14/node_modules/zod/v4/core/schemas.js:865
directus-development | const first = def.options[0].zod.run;
directus-development | ^
directus-development |
directus-development | TypeError: Cannot read properties of undefined (reading ‘run’)
directus-development | at file:///directus/node_modules/.pnpm/zod@4.0.14/node_modules/zod/v4/core/schemas.js:865:39
directus-development | at Function.init (file:///directus/node_modules/.pnpm/zod@4.0.14/node_modules/zod/v4/core/core.js:14:9)
directus-development | at file:///directus/node_modules/.pnpm/zod@4.0.14/node_modules/zod/v4/classic/schemas.js:544:20
directus-development | at Function.init (file:///directus/node_modules/.pnpm/zod@4.0.14/node_modules/zod/v4/core/core.js:14:9)
directus-development | at file:///directus/node_modules/.pnpm/zod@4.0.14/node_modules/zod/v4/classic/schemas.js:556:14
directus-development | at init (file:///directus/node_modules/.pnpm/zod@4.0.14/node_modules/zod/v4/core/core.js:14:9)
directus-development | at new ZodDiscriminatedUnion (file:///directus/node_modules/.pnpm/zod@4.0.14/node_modules/zod/v4/core/core.js:31:9)
directus-development | at Module.discriminatedUnion (file:///directus/node_modules/.pnpm/zod@4.0.14/node_modules/zod/v4/classic/schemas.js:561:12)
directus-development | at file:///directus/node_modules/.pnpm/@directus+api@file+api@types+node@24.2.0_jiti@2.5.1_typescript@5.8.3/node_modules/ /api/dist/websocket/messages.js:4:36
directus-development | at ModuleJob.run (node:internal/modules/esm/module_job:345:25)

1 Like
2

Hey @xluckydegen, we’re aware of the issue with the experimental m2a extension and a PR has been submitted on it. Would you mind sharing which other extensions you’re running into issues with? Thanks, Beth

3

Sure, I just tried them one by one, and these are the ones that are currently not working (from my Dockerfile):

RUN pnpm i --prod directus-labs/command-palette-module
RUN pnpm i --prod directus-labs/experimental-m2a-interface
RUN pnpm i --prod directus-labs/flow-trigger-bundle
RUN pnpm i --prod directus-labs/liquidjs-operation
RUN pnpm i --prod directus-labs/multilevel-autocomplete-api-interface
RUN pnpm i --prod directus-extension-generate-types

RUN pnpm i --prod directus-extension-sync
RUN pnpm i --prod directus-sync
RUN pnpm i --prod directus-extension-schema-sync

Some are not so important for me, but for example directus-sync is currently must-have for me (I know it’s not directly from directus-labs, but very handful extension). The same for flow-trigger-bundle.

5

For anyone struggling with the same issue, I just found a solution.

The pacote utility does exactly what’s needed: instead of performing a full install, it simply extracts the tarball from npm. Using this approach, the extension works as expected.

You can “install” the extension like this:

RUN npx --yes pacote extract @directus-labs/experimental-m2a-interface@1.2.1 /directus/extensions/experimental-m2a-interface

The extension then runs correctly.

I hope this helps others!

6

Thank you for coming back and sharing your solution before I was able to return with an answer for you, I’m glad you’ve got them working again. I’ve marked this as answered, do let us know if anything else pops up please.