Replies: 1 comment
-
@emazzu , the Loopback 4 File transfer example shows how well other packages like Multer can fit in the framework architecture with artifacts like Service providers. The example exposes a Multer middleware thru this provider, hence the storage component and core file handling belongs to Multer itself not loopback 4. Having said that, with that example you have the building blocks to integrate other packages related to Multer such as Multer S3 or Multer Azure and build your application or micro service according to your needs. Loopback4 provides already all the tools with composability and modularity in mind that you can use . |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, how arew you ??
I would like to know, if in lb4, component storage is replaced by multer, and if with multer I can connect to aws, azure, file system, etc. or now exist distinct connector for each case.
Regards
Eduardo
Beta Was this translation helpful? Give feedback.
All reactions