Feat/spec renderer resolved

[jackkav]

Motivation: use internel spec renderer, over swagger-ui-dist
Aim: drop-in replacement
Todo:

• add and use @kong/spec-renderer
• remove swagger-ui-dist
• point at spec-renderer stable build
• confirm behaviour and layout meets aim
• scroll overflow
• color themeing decision, either dark/light or take something similar to our css variable palette

Future work

• use bundler type module resolution in insomnia

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[adamdehaven]

color themeing decision, either dark/light or take something similar to our css variable palette

@jackkav for now, we'd recommend utilizing the default theme (light) in the short term. There is theming available currently via CSS Custom Properties; however, we're going to bake-in easier theming and possibly a default dark theme that you can then tweak for Insomnia specifically. We're working with Design on getting some "official" themes, so recommended to hold on working on customizing on your own in the short-term

[jackkav]

I was trying to fix the styling and I encountered a couple of dx issues,

1. the vite dev server started opening a chrome tab on save
2. a new error is appearing in the console Warning: You are calling ReactDOMClient.createRoot() on a container that has already been passed to createRoot() before. Instead, call root.render() on the existing root instead if you want to update it.

[adamdehaven]

I was trying to fix the styling and I encountered a couple of dx issues,

1. the vite dev server started opening a chrome tab on save

I'm not sure on this one; nothing in the web component should be triggering this?

2. a new error is appearing in the console Warning: You are calling ReactDOMClient.createRoot() on a container that has already been passed to createRoot() before. Instead, call root.render() on the existing root instead if you want to update it.

This typically happens when a DOMContentLoaded event listener is triggered twice. Is there any chance this line is getting called more than once?

Additionally, do you need to unmount the web component at some point, e.g. root.unmount()?

[adamdehaven]

We merged in the changes from this PR preview into main for now (still need to resolve exports, etc.) but you can install the latest

npm i @kong/spec-renderer-dev@latest

[jackkav]

Both issues could be caused by the place we register I can try a few other places that are more likely to only eval once

[jackkav]

above idea didn't work, looks like the spec renderer register function is interfering with vite HMR in insomnia.
moving discussion to #8036