Closed ueberBrot closed 7 months ago
I found the issue for my problem. It was an independent issue with Nx. Nx was experiencing problems with the implicit imports of the adapter packages and did not include it in the final build.
I solved the issue by importing them explicitly.
I saw in your code that you're using the AdapterLocal.ts
as a fallback, but since it's not in the bundle, this does not work. This should get fixed.
Also question: Is there a specific reason for individual packages for all adapters instead of using the local files in the storage-abstraction
package?
All adapters are separate packages that you have to install explicitly. This way your package will only contain code that it actually needs.
I saw in your code that you're using the AdapterLocal.ts as a fallback, but since it's not in the bundle, this does not work. This should get fixed.
This is intentionally. The fallback to a local file allows you to work on the Storage Abstraction package and all adapter packages in one code base. Only when published to npm the code is split up into (at the moment) 7 separate packages.
I use the following package combination:
"@tweedegolf/sab-adapter-amazon-s3": "1.0.12" "@tweedegolf/sab-adapter-local": "1.0.5" "@tweedegolf/storage-abstraction": "2.1.1"
I get the following error message:
The
AdapterLocal
package is missing in thedist
folder as you can see on the npm package index:Additional information:
And the code snippet: