@Unlocked Packages, we are using the package strategies for the upcoming applications in our ORG. But when creating the unlocked packages, I am seeing some strange issues. Here are the two issues I see when creating package versions
1. Compilation issue
When executing the force:source:push everything looks good with no compilation errors. But when creating a package version, I am getting this issue. But, after 2-3 retrying attempts to create the package version, It would be successful. This is even happening in case of package upgrade with the same error. But, the package upgrade works fine after 2-3 retrying upgrade attempts. I even googled with this error but no luck. What exactly is this error mean? I am getting too frequently these days.
ERROR running force:package:version:create: : Compilation Failure
/c/ak_page/ak_page.js:0,0 : LWC1002: Error in module resolution: Maximum call stack size exceeded,ak_page: Compilation Failure
/c/ak_page/ak_page.js:0,0 : LWC1002: Error in module resolution: Maximum call stack size exceeded
2. Error with non-related components while creating the package versions
While creating package version today, I got this issue. I am seeing errors with unrelated components. We even don't have any components with these names in our ORG/package. Why am I seeing these issues. But re-executing the creation worked fine. We have a package dependency on 04t4N000000omLKQAY package, but it's showing me 04t4N000000omLK in the logs with the following exceptions. These are not part of our ORG/Package.
Request in progress. Sleeping 30 seconds. Will wait a total of 6000 more seconds before timing out. Current Status='Queued'
Request in progress. Sleeping 30 seconds. Will wait a total of 5970 more seconds before timing out. Current Status='Verifying dependencies'
ERROR running force:package:version:create: An error occurred while trying to install a package dependency, ID 04t4N000000omLK: IMS_ViewBOLPdf: Invalid definition for null:IMS_ViewBOLPdfController: ApexService.getType() return null with currentNamespace: c, namespace: null, name: IMS_ViewBOLPdfController
Appreciate your response.
@Marc Behr The package creation is not taking 2hrs. What I said is that it is taking 2-3 attempts to create the package. The package creation just takes 5-10 min if its success. (we have a couple of dependent packages for code reuse)
The package we are trying to build is very minimal with
7 LWC components
50 classes contain interfaces, selectors..etc with SOC patterns depending on the fflib implementation (The dependencies I mentioned is the fflib package we built internally as an unlocked package)
5 mdt components
7 aura components
10 fields across the different standard object
It takes only 5-7 min max if its success in creating the package version. And also takes only a few mins while installing the package too. Also, all the dependent packages I mentioned are all internal packages created with our PROD devhub.
something going wrong with the cross-references like I mentioned (IMS_ViewBOLPdfController is not part of any of our dependencies).
