Hi! We’re running into an issue that left us without many ideas left of what might be happening. The goal is transform our Stencil components into Angular and React outputs, then run their respective builds though an automated GitLab pipeline. This is how the stencil.config.ts looks like currently:
export const config: Config = {
namespace: 'core',
outputTargets: [
{
type: 'dist',
esmLoaderPath: '../loader'
},
{
type: 'dist-custom-elements',
customElementsExportBehavior: 'auto-define-custom-elements',
externalRuntime: false
},
angularOutputTarget({
componentCorePackage: '[our-internal-package]',
outputType: 'standalone',
directivesProxyFile: '../adapters/angular/src/lib/generated/components/proxy.ts',
directivesArrayFile: '../adapters/angular/src/lib/generated/components/index.ts'
}),
reactOutputTarget({
outDir: '../adapters/react/src/lib/generated/components/'
})
]
};
When running Stencil’s build locally, we get all the files correctly created. The issue is that when doing so in the pipeline, followed by Angular’s build command, we get the following:
When checking the artifacts of that failed pipeline, no utils is present even if previously pushed by running it locally. This implies that at the moment of rebuilding Stencil, the file is replaced incorrectly somehow. Below is how the structure is set when running locally or on remote before executing the automated task:
Any ideas on what might be happening and how to tackle this?
Thank you in advance!