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
When running plugins in parallel or running same plugin multiple times for different audits it overrides its runner config as the folder for each individual runner config is node_modules/.code-pushup/<plugin-name>.
What would you expect to happen?
Each runner of individual plugins should have its own unique folder to hold the config file and output file.
This can be achieved by adding one more level of nesting into runners folder as in node_modules/.code-pushup/<timestamp>/<plugin-slug>.
Also plugin slug should be used instead of hardcoded plugin name as it will be more versatile if people would reuse or extend existing plugins with their own variety (for example duplicating coverage plugin execution to get two reported coverages, one from Jest and one from Cypress component tests)
What steps did you take?
Setup Code PushUp target with ESLint for multiple projects in one Nx monorepo
For better reproduction have different lint rules setup in the projects
Run plugins in parallel or via affected
Observe errors of rules not being found or other weird behavior related to overridden runner config
Code PushUp package version
latest
What operation system are you on?
Windows
Node version
22
Relevant log output
The text was updated successfully, but these errors were encountered:
What happened?
When running plugins in parallel or running same plugin multiple times for different audits it overrides its runner config as the folder for each individual runner config is
node_modules/.code-pushup/<plugin-name>
.What would you expect to happen?
Each runner of individual plugins should have its own unique folder to hold the config file and output file.
This can be achieved by adding one more level of nesting into runners folder as in
node_modules/.code-pushup/<timestamp>/<plugin-slug>
.Also plugin slug should be used instead of hardcoded plugin name as it will be more versatile if people would reuse or extend existing plugins with their own variety (for example duplicating
coverage
plugin execution to get two reported coverages, one from Jest and one from Cypress component tests)What steps did you take?
Code PushUp package version
latest
What operation system are you on?
Windows
Node version
22
Relevant log output
The text was updated successfully, but these errors were encountered: