MichaelV

Add the whole report to the outputs as a outputs.result or outputs.report

1

Then we would be able to add it as a sticky comment to th PR, or pipe it to somewhere else

When the time increases "faster" is written and when it decreases "slower". It should be the other way around. I believe this is the culprit- https://github.com/stephencookdev/speed-measure-webpack-plugin/blob/ca66781752e4d11a0730a444b7c21947a569cd1b/index.js#L129 Example of an output...

SyntaxError: Named export 'GLOBSTAR' not found

3

### Environment We are running version `^2.8.0`. Once in a while, we start having persistent errors like this- ``` failed to load config from ***/vite.config.mjs error during build: import {...

While using performance.measure(...) the detail fields isn't passed on to the PerformanceObserver since Node V20

3

### Version 20 ### Platform Mac ### Subsystem perf_hooks ### What steps will reproduce the bug? ```js const { performance, PerformanceObserver } = require('perf_hooks'); const perfObserver = new PerformanceObserver((items) =>...

## Which issues does it affect? - https://github.com/OS-Guild/monitored/issues/20 ## What it does This feature adds a support for [lambda EMF custom metrics ](https://docs.aws.amazon.com/lambda/latest/operatorguide/custom-metrics.html)

### Acknowledgements - [x] I read the documentation and searched existing issues to avoid duplicates - [x] I understand this is a **bug tracker** and anything other than a proven...

// sampleTest.spec.ts ``` describe("sample test", () => { it("should be true", () => { require("snappy"); }); }); ``` Output ``` ➜ js-playground yarn jest src/__tests__/sampleTest.spec.ts --detectOpenHandles yarn run v1.22.22 warning...