You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a library with many components having stylings
Run yarn run cms-adapters at root
Notice the time it takes for nx run @mypackage:"cms-adapters:style"
Current result
In our case, this cms-adapters:style step is taking ~7m30s for a package containing around 100 components
Expected result
Can we optimize the process to reduce the processing time? As globally this step has a high impact on our current build statistics.
Additional comments
The text was updated successfully, but these errors were encountered:
Thank you for the report.
The process cms-adapters:style is actually using the Sass API and rebuild each Sass files matched by its input patterns.
The performance issue can be due to import of a large amount of Sass dependencies (direct or indirect) in every Sass parsed.
Is it a new issue you faced after an update of the Otter library? Can it be due to an update or your Sass architecture on your side? Or is it an issue you have since long time?
The issue started when we added the extraction and check of the CMS metadata in our pipeline (brown + orange in the screenshot), the build step is now longer which makes the overall pipeline close to the 1h which is the time-out limit we have in our current set-up.
Package name
extractors
Package version
11.0.4
Reproduction steps
Create a library with many components having stylings
Run
yarn run cms-adapters
at rootNotice the time it takes for
nx run @mypackage:"cms-adapters:style"
Current result
In our case, this
cms-adapters:style
step is taking ~7m30s for a package containing around 100 componentsExpected result
Can we optimize the process to reduce the processing time? As globally this step has a high impact on our current build statistics.
Additional comments
The text was updated successfully, but these errors were encountered: