single-spa/Deploy to import-map-deployer
Deploy a microfrontend or import map via import-map-deployer
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| host | The origin of the import-map-deployer server. Example https://deployer.example.com | yes | — |
| environment-name | The import-map-deployer environment to deploy to. If not provided, the default environment will be used. | no | — |
| service-name | The name of the service (microfrontend). This service name appears in the imports section of the import map | no | — |
| service-url | The url of the service (microfrontend). This appear as the value in the imports section of the import map | no | — |
| service-integrity | The integrity of the file of the service-url, added to the integrity section of the import map. This is for security reasons | no | — |
| service-integrity-file-path | The file path of the file of the service-url, which will be checksum'ed and added to the integrity section of the import map. This is for security reasons | no | — |
| service-package-dir-level | An integer that determines the "packages via trailing slashes" entry in the import map. See https://github.com/single-spa/import-map-deployer?tab=readme-ov-file#patch-servicesenvstagepackagedirlevel1 | no | — |
| import-map-path | The file system path of an import map to be patched | no | — |
| username | The username used in HTTP basic authentication with import-map-deployer | no | — |
| password | The password used in HTTP basic authentication with import-map-deployer | no | — |
Outputs
no outputs