From 2bdc065c7e974338a623fba6e1ffc69622209f11 Mon Sep 17 00:00:00 2001 From: hlaunay Date: Thu, 9 Nov 2023 11:58:08 +0100 Subject: [PATCH] import-map-storage-helper recommendation --- versioned_docs/version-5.x/recommended-setup.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/versioned_docs/version-5.x/recommended-setup.md b/versioned_docs/version-5.x/recommended-setup.md index 117a179ba..f6f227d7c 100644 --- a/versioned_docs/version-5.x/recommended-setup.md +++ b/versioned_docs/version-5.x/recommended-setup.md @@ -290,6 +290,8 @@ The advantage of b) is that it doesn't require running the import-map-deployer i Another option of deploying and making sure the latests javascript files are beeing used is making use of redirect (HTTP status code 302). The single-spa import map uses the unhashed url of the javascript file. eg: dist/app.js. Then when the requests for this file comes to the server it is redirected to the actual deployed file eg. dist/app.123abc.js and this is then served to the client. This way the import map never has to be updated and the microfrontend can be separately deployed. +Continuous integration leads to the creation of a large number of packages. [import-map-storage-helper](https://github.com/dolmen-tech/import-map-storage-helper) can be a solution to clean up outdated and unused packages in the case of a CDN + [import-map-deployer](https://github.com/single-spa/import-map-deployer) usage. + ## Applications versus parcels versus utility modules Single-spa has [different categories](/docs/microfrontends-concept#types-of-microfrontends) of microfrontends. It is up to you where and how you use each of them. However, the single-spa core team recommends the following: