We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We should augment the logs with information about memory usage during the analysis.
We need to investigate available APIs
We could observe heap after each file and print summary at the end of analysis for JS/TS sensor.
TBD if something is needed for CSS sensor
The text was updated successfully, but these errors were encountered:
as discussed with @saberduck, we should do a dedicated sprint for this one, so I'm removing it from the hardening.
Sorry, something went wrong.
Completed with:
sonar.javascript.node.debugMemory
No branches or pull requests
We should augment the logs with information about memory usage during the analysis.
We need to investigate available APIs
We could observe heap after each file and print summary at the end of analysis for JS/TS sensor.
TBD if something is needed for CSS sensor
The text was updated successfully, but these errors were encountered: