perf: research building output targets separately from calcite-components

[benelan]

Description

Our monorepo follows Stencil's output targets example project, where the React output target is built every time the web components build. Building CCR isn't necessary for most of our day-to-day development, so it would be nice to split that process into a separate step.

Proposed Advantages

Build performance, although I doubt generating the CCR source takes very long since it is so small.

Which Component

Stencil/monorepo configuration

Relevant Info

#6988 (comment)

[geospatialem]

Effort requires build benchmarking to determine if the above is feasible and should be adopted.

Some opportunities for the above:

• Change the name of the framework output target build in the npm script so it doesn't get included in turbo's build pipeline.
• Determine if a few lines during the CC build (which takes the majority of the build time) could be removed and determine if it saves time.
• If deemed worthy, create a separate stencil config file, similar to Storybook.

[jcfranco]

Is this still valid after #10310?

[benelan]

I just tested and it's still valid. If you delete packages/calcite-components-react/src/components.ts and then run npm run --workspace @esri/calcite-components build, the deleted file will be re-generated. IIRC you asked me to log this, but I really don't think the performance improvement would be noticeable like I mentioned above.

[benelan]

My suggestion would be to close it as not planned, but up to you @jcfranco