how to use nebulaLogger in namespace unmanaged packaged environment

[akhtarhm]

Hi @jongpie I have installed unlocked nebulalogger in my sandbox and added the nebula apex, lwc code snippets in my apex classes and components. My sandbox components are deployed to prod with unmanaged packaged using namespace.

so question here is do i need to package the nebulalogger with same namespace that my production has or how it is?
How should I use nebula code in my packaged code which has namespace, Please suggest.

Thank you!!

[akhtarhm]

Any suggestions @jongpie will be much appreciated.

[jongpie]

Hi @akhtarhm - apologies for the late response! Could you clarify some details on your situation? Is your namespaced package something that will only be used internally at your company? Or will the package be installed in multiple client orgs?

[jongpie]

Hi @akhtarhm - a couple of follow up questions for you:

1. I was under the impression that you are building your own package, and that your own package has a namespace - but based on your first screenshot of sfdx-project.json, it seems as though you don't have a namespace set, nor does it look like you're building a package. Can you clarify on your scenario? Are you simply deploying metadata to your org? Or are you actually creating package versions & installing those in your orgs?
2. For your second screenshot that says "No MODULE named Nebula:logger found", do you have the Nebula Logger managed package installed in the target org? You'll need to have the managed package already installed in the org before you deploy/install your own metadata.

[akhtarhm]

Thanks for reply @jongpie. My reply:

1. The 1st screenshot is from my dev sb where i am trying to add nebula code in my LWC. Yes we do packaging but not in dev sb, we have separate packaging environment against which our PR validated. Basic flow goes like: Dev sb ---> Packaging environment ---> QA environment ---> Production environment. I have installed the nebula package in my Dev sb, trying to add nebula LWC code in my components so that i can push those changes to Packaging environment where we will build our own package with namespace DeltakSRP. Once packaging completed, we will install our own package + nebula package in QA environment and so on.

2. Yes, I do have manage nebula with in my target environment where i am trying to deploy.

Please suggest how I should process

[akhtarhm]

As per below documentation, we can't use lwc from another namespace in our custom component:

1. https://ideas.salesforce.com/s/idea/a0B8W00000GdXQ3UAN/use-a-lightning-web-component-from-another-packagenamespace
2. https://salesforce.stackexchange.com/questions/301980/not-being-able-to-reference-packaged-custom-lwcs-from-other-lwcs-outside-the-pac?rq=1

[jongpie]

@akhtarhm this is now available in v4.13.0