Unable to install extensions from the Directus Marketplace

[shrey]

In the latest version of Directus (v10.10.1), i'm unable to install any extension from the in-built marketplace.

Example--

Click on Install Extension

---

Error popup received.

Error logs:

Mar 07 21:08:12[15:38:11] GET /extensions/registry/extension/647aa4e9-91ef-4b17-b00d-d07d1775ddad 200 1.1s
Mar 07 21:08:16"code": "ENOENT",
Mar 07 21:08:16"code": "ENOENT",
Mar 07 21:08:16"errno": -2,
Mar 07 21:08:16"errno": -2,
Mar 07 21:08:16"message": "ENOENT: no such file or directory, lstat 'node_modules/.directus/marketplace/dea64409-1e76-4857-aedc-2b0f76c1e856'",
Mar 07 21:08:16"message": "ENOENT: no such file or directory, mkdir 'node_modules/.directus'",
Mar 07 21:08:16"path": "node_modules/.directus"
Mar 07 21:08:16"path": "node_modules/.directus/marketplace/dea64409-1e76-4857-aedc-2b0f76c1e856"
Mar 07 21:08:16"stack":
Mar 07 21:08:16"stack":
Mar 07 21:08:16"syscall": "lstat",
Mar 07 21:08:16"syscall": "mkdir",
Mar 07 21:08:16"type": "Error",
Mar 07 21:08:16"type": "Error",
Mar 07 21:08:16Error: ENOENT: no such file or directory, lstat 'node_modules/.directus/marketplace/dea64409-1e76-4857-aedc-2b0f76c1e856'
Mar 07 21:08:16Error: ENOENT: no such file or directory, mkdir 'node_modules/.directus'
Mar 07 21:08:16[15:38:16.319] WARN: ENOENT: no such file or directory, mkdir 'node_modules/.directus'
Mar 07 21:08:16[15:38:16.320] ERROR: ENOENT: no such file or directory, lstat 'node_modules/.directus/marketplace/dea64409-1e76-4857-aedc-2b0f76c1e856'
Mar 07 21:08:16err: {
Mar 07 21:08:16err: {
Mar 07 21:08:16}
Mar 07 21:08:16}
Mar 07 21:08:17[15:38:16] POST /extensions/registry/install 500 602ms
Mar 07 21:08:20[15:38:20] GET /server/ping 200 6ms

[nebulon]

Is this marketplace new or if not was it working before?

[shrey]

@nebulon This is a new feature.

[shrey]

Hi @nebulon , any update regarding this?

[nebulon]

This should be fixed now with latest package. Unfortunately I found that if a previous extension installation failed, the database would contain that info, making it impossible to install the same extension again. So you may have to manually delete records from the database to get over this