Can not install extensions SDK

[t-kawatsu]

Preflight Checklist

• I have completed all Troubleshooting Steps.
• I'm on the latest version of Directus.
• There's no other issue that already describes my problem.

Describe the Bug

/directus/extensions/interfaces $ npm i -D @directus/extensions-sdk

up to date, audited 1138 packages in 2s

87 packages are looking for funding
  run `npm fund` for details

6 high severity vulnerabilities

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

/directus/extensions/interfaces $ npm audit fix --force
npm WARN using --force Recommended protections disabled.
npm WARN audit Updating sqlite3 to 1.7.3,which is a SemVer major change.
npm WARN audit No fix available for directus@*
npm WARN audit Updating connect-session-knex to 1.7.3,which is a SemVer major change.
npm WARN tarball tarball data for directus@file:directus-9.0.0-rc.95.tgz (null) seems to be corrupted. Trying again.
npm WARN tarball tarball data for directus@file:directus-9.0.0-rc.95.tgz (null) seems to be corrupted. Trying again.
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /directus/directus-9.0.0-rc.95.tgz
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/directus/directus-9.0.0-rc.95.tgz'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/node/.npm/_logs/2021-10-06T05_43_14_669Z-debug.log

To Reproduce

/directus/extensions/interfaces $ npm i -D @directus/extensions-sdk

up to date, audited 1138 packages in 2s

87 packages are looking for funding
  run `npm fund` for details

6 high severity vulnerabilities

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

/directus/extensions/interfaces $ npm audit fix --force
npm WARN using --force Recommended protections disabled.
npm WARN audit Updating sqlite3 to 1.7.3,which is a SemVer major change.
npm WARN audit No fix available for directus@*
npm WARN audit Updating connect-session-knex to 1.7.3,which is a SemVer major change.
npm WARN tarball tarball data for directus@file:directus-9.0.0-rc.95.tgz (null) seems to be corrupted. Trying again.
npm WARN tarball tarball data for directus@file:directus-9.0.0-rc.95.tgz (null) seems to be corrupted. Trying again.
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /directus/directus-9.0.0-rc.95.tgz
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/directus/directus-9.0.0-rc.95.tgz'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/node/.npm/_logs/2021-10-06T05_43_14_669Z-debug.log

What version of Directus are you using?

9.0.0-rc.95

What version of Node.js are you using?

16.10.0

What database are you using?

Postgres 12

What browser are you using?

Chrome

What operating system are you using?

docker-compose

How are you deploying Directus?

Docker

[azrikahar]

are you running the command inside the docker container?

I believe it would be better to move your extensions setup outside of the directus extensions directory and do the installation there. After that, you will only need to move the content of dist folder into directus/extensions/interfaces/<your-interface-name>. More info here: https://docs.directus.io/guides/interfaces/#_4-build-and-deploy

I'm sure @nickrum can offer a better insight here 👍

[nickrum]

There isn't much I can add to that 👍

The docker image uses tar packages instead of installing the Directus packages from npm. I would assume the npm audit fix --force has somehow corrupted one of those tarballs. It's indeed better to build your extensions separately and then copy them into a mounted directory.