Library setup with more than one decorator definition file

[Onokaev]

I'm having a small issue with my library setup. I have two sets of decorator definitions that I want to be under different namespaces. This means I'll have a main namespace NamespaceMain and two sub-namespaces NamespaceMain.A and NamespaceMain.B.
When I add the sub-namespaces to the decorator definitions, the compiler is not finding the js implementations of the decorators. Everything works when I remove the sub-namespace definitions, but now everything appears under the main NamespaceMain

My intention is to have users use either NamespaceMain.A or NamespaceMain.B, or both. When only using NamespaceMain.A, the user should not have access to items in NamespaceMain.B

If only NamespaceMain is used, there should be warnings/errors.

Is this possible to implement currently? How does the folder structure change with the extra namespaces?

[timotheeguerin]

Use the new $decorators to define all your decorators instead of exporting each one

https://typespec.io/docs/extending-typespec/create-decorators/#javascript-decorator-implementation

You can also try tspd to generate their signature

[Onokaev]

This is what I needed. Thanks!
I moved my decorators to use this https://typespec.io/docs/extending-typespec/create-decorators/#javascript-decorator-implementation approach.