Hi @johnjenkins, would these changes extend to the framework adapters OOTB/'as is', or would that require additional changes in the output-targets repo?

We're running a React MFE architecture and would really benefit from being able to transform the tags at runtime to avoid version registration clashes between feature teams running different versions of the stencil component lib - just wondering whether these changes could facilitate that in future.

Thanks!

hey @elliottdaviesss - Thanks for the interest!

Yes, it would involve some tweaks in the output adapters (wrapping tagName references in the newly exported transformTag(tagName))

On reflection, idk if what i've done here is the best approach; @Cliffback has came up with a slightly different strategy which you can use at https://github.com/Cliffback/stencil-custom-suffix-output-target (doesn't work with react output atm I think).
I like the fact it's an output target, plus it does some extra bits like transforming css selectors.

hey @elliottdaviesss - Thanks for the interest!

Yes, it would involve some tweaks in the output adapters (wrapping tagName references in the newly exported transformTag(tagName))

On reflection, idk if what i've done here is the best approach; @Cliffback has came up with a slightly different strategy which you can use at https://github.com/Cliffback/stencil-custom-suffix-output-target (doesn't work with react output atm I think). I like the fact it's an output target, plus it does some extra bits like transforming css selectors.

@johnjenkins I could give transforming the other output targets the same way, so that it would work with react as well?

My main focus has been on angular so far, as that is what we need at work, but would be nice to expand it now that it is on npm regardless