Would be nice to figure out why there are errors after npm start and get rid of them.

Can't seem to see parcels in the list but when I do the devtools config I can see them in the UI with overlays on.

From: https://single-spa.js.org/docs/devtools

  color: "#000", // the default for this is actually based on the app's name, so it's dynamic. can be a hex or a CSS color name

  background: "#000", // the default for this is actually based on the app's name, so it's dynamic. can be a hex or a CSS color name

These seem to always be black here: https://react.microfrontends.app/people

Hi I use "single-spa-inspector" but I have a small problem my SPA (utility module) does not appear in the list, so impossible to override the path ...

Is is expected ?
Thanks for your help !

Helper libraries such as single-spa-vue, single-spa-angular, and single-spa-react all implement a default dom element getter now that appends a div to the dom with an html id that follows a certain convention.

Single-spa-inspector could check if that html id exists when looking for a div to append overlays to. This would be awesome because then single-spa users don't even have to do export const devtools from their apps. See related single-spa/single-spa-react#51.

App names such as @openmrs/esm-devtools are not being properly escaped as CSSOMStrings, and so the corresponding node isn't being found and the overlay isn't being created. It would need to use CSS.escape() to derive the app names into valid selectors.

When demoing to potential consulting clients, or just trying to explain which applications are active to devs new to single-spa, I like seeing all the overlays at once.

Having a button to toggle them all off/on at once would be cool.

Single-spa-inspector is still in use, but its API has been limited because it doesn't interop with SystemJS and relies on single-spa's API only. In order to keep it alive and help provide the community value, I'm proposing that this extension should be updated and use import-map-overrides. The main idea is to rely on the import-map-overrides JS API to implement all if not most of the current features, on top of upgrading deps and build configuration.

Opening this as an RFC in order to:

• begin gauging community value
• ask for community involvement

If you'd like to see single-spa-inspector updated, please leave a 👍🏼 on this comment. If you'd like to be involved in this development effort, please DM me in the single-spa Slack workspace and reference this issue.

I rest my case.

I think it's because the table is height 100%.

This would be a great beginner bug to work on if anyone is interested.

now that we can use github actions and @filoxo has implemented an easy-to-use script, we should be able to fairly easily setup auto deployments.

The question I have is: when should a deployment happen?

• On every merge to master?
  • The potential problem with that is that we have to update the manifest version for the new version to work, and there's the possibility that we forget and then the deployment fails
• On every new tag?
  • I'm not even sure this is possible with github actions, but I think it has the potential to be the more foolproof way of dealing with potential deployment issues on master
• Others?

When an app resizes, the overlay does not until it is removed and readded. In this example, navbar-ui had had a banner displayed above it. When I dismissed that banner, the overall size of navbar-ui changed but the overlay is still the original size.

Currently the inspector only shows registered applications and it doesn't show any other mfe types.

This introduces a weird disconnect where this tool doesn't work great with the recommended approach. Import-map-overrides has features this doesn't have that directly relate to a single-spa application.

Error during addOverride. An unexpected error occurred

Uncaught (in promise) Error: eval Cmd 'window.SINGLE_SPA_DEVTOOLS.exposed Methods.getRawAppData()' failed: {"code":"E_PROTOCOLERROR","description":"Inspector protocol error: %s","details":["Object reference chain is too long"],"isError":true}

Google Chrome
Version 90.0.4430.212 (Official Build) (x86_64)

there is no table rows displayed in the inspector.
I have tested imports-map-override like the below:
`html

<import-map-overrides-full
show-when-local-storage="devtools"

`
it works well, but the single-spa-inpector always displays empty rows,it seems that no apps to display.

Since working for quite some time with the inspector, its very powerful!
Can we further improve it by add a toggle that can temporary disable an override? This would help a lot 👍

Having screenshots or even a gif of the inspector in action would be great!

https://github.com/mozilla/web-ext/releases/tag/3.2.0

Upgrading would also allow us to develop in Chrome too!

When manually unmounting an app, the overlay is not being removed. In this example below, I've manually toggled navbar-ui and at the top you can still see the overlay title visible (but cut off).

currently I'm just doing it manually. it would be great to add a script that does it for us though.

For Chrome, I think it's possible to do that at the moment.

For FF, I don't entirely know if the whole process can be automated at the moment or not. See this thread and comment: mozilla/web-ext#804 (comment)

I do not want the user to be able to manipulate the site

The ability to browse/link my import-map to allow for a quick auto-fill of app override locations would be nice :)

Now that Edge is Chromium-based, we should be able to submit the Chrome build almost as-is, just with a modification to descriptions in the manifest files (I saw a Preact core team member report that this is possible, on Twitter). Might also investigate if we can add it as a build target in wext/shipit.

https://chrome.google.com/webstore/detail/single-spa-inspector/emldbibkihanfiaiaghebffnbahjcgcp

Cannot install the extension.

Version 72.0.3626.119 (Official Build) (64-bit)

Mac os 10.14.3 (18D109)

I wasn't able to find any issues about this in the web-ext repo, so I think it may have to do with something that I've just misconfigured...? Anyway, when you run npm run start:firefox, my CPU usage for node goes up to ~370% :(

The sort order of the apps is now reversed so mounted apps are shown last. These should be sorted alphabetically with mounted apps grouped first.