It's just a general error post-installation

Trying to debug what the issue is though. Is there a way to serve the built packages locally?

(instead of the dev server)

Currently im making incremental guesses and pushing releases to try to fix

Might need a little more detail though on what error you're seeing in order to help you debug or to point out other debugging methods. As of right now it sounds like it's installing correctly but perhaps not loading.

There's likely some sort of error in the package, but it's packaging without issue so it's tough to tell what is wrong

Serving the packages will give me a good starting point

I'm taking a break from it for a sec, but that's where I'm working. I definitely think I'm chasing a broken custom component in pkg/app-launcher, it's just tough to debug

Ah, I think the culprit is that we're using the composition API: https://vuejs.org/guide/typescript/composition-api.html#typing-component-props

<script lang="ts" setup>

which might be compatible with the dev tools but not the webpack build

Should I open an issue about that, or do you think support for that will come with some of the behind-the-scenes work going on right now? (there might also already be a ticket)

For what it's worth, there is a

debug

property on the

ui-plugin-operator

chart that can be enabled to get a much better picture of what's going on behind the scenes. Although this wouldn't log the issue you were running into, it can certainly help narrow down further issues.

we're going to refactor the component in the short term to make sure it conforms, and to get an initial release published, then hopefully break more things after that