When JSPM is down, our pipeline is currently blocked due to the reliance on the jspm generator to retrieve information about packages and generate the importmap. As a result, the asset server build fails intentionally to prevent publishing a broken importmap. However, in certain situations, we may not need to rebuild the importmap or download new packages, such as when there are no updates or changes to the dependencies.
To address this issue, we could implement a mechanism to determine whether the importmap needs to be rebuilt based on the changes made to the project's dependencies. This could involve comparing the previous state of the dependencies with the current state to determine if any updates or changes were made. If no changes were made, then the pipeline could be allowed to continue without rebuilding the importmap.
This feature could potentially enable us to deploy patches even when JSPM is down by skipping the importmap generation step in the pipeline.
When JSPM is down, our pipeline is currently blocked due to the reliance on the jspm generator to retrieve information about packages and generate the importmap. As a result, the asset server build fails intentionally to prevent publishing a broken importmap. However, in certain situations, we may not need to rebuild the importmap or download new packages, such as when there are no updates or changes to the dependencies.
To address this issue, we could implement a mechanism to determine whether the importmap needs to be rebuilt based on the changes made to the project's dependencies. This could involve comparing the previous state of the dependencies with the current state to determine if any updates or changes were made. If no changes were made, then the pipeline could be allowed to continue without rebuilding the importmap.
This feature could potentially enable us to deploy patches even when JSPM is down by skipping the importmap generation step in the pipeline.