ehmicky

Yes, I am realizing that we are talking about the same thing as well! :) I.e. getting error rates for particular sub-stages of `@netlify/build`. From that angle, I understand now...

This [specific commit](https://github.com/ehmicky/cv-website/commit/23bca413c1b3a14fccb46361450916fe00c8e6e3) is an example of a site using both a [`*.js` function](https://github.com/ehmicky/cv-website/blob/main/netlify/functions/typescript.js) and a [`*.ts` function](https://github.com/ehmicky/cv-website/blob/main/netlify/functions/typescript.ts). [Both functions are being bundled](https://app.netlify.com/sites/mick/deploys/6140b89f1b607c00083e4e1e#L388): ``` Packaging Functions from netlify/functions directory: -...

This makes sense!

After some discussion with @JGAntunes, we have been considering the following implementation: - Add a `--debugOutput` CLI flag to `@netlify/build` and `@netlify/config` - That flag takes either a file path...

Yes absolutely! We have discussed adding a `onPreInstall` event in Build plugins. This could run before `npm install` and `yarn`. However until we move the other installations command for other...

`onPreInstall` tracked separately at #1149.

Hi @rvanmil, This feature is on our roadmap. Implementing it requires some refactoring described at #1178 to be done first, which has delayed doing it. However we are looking into...

Thanks for reporting this @mateuszkocz @kitop @keiko713 `cancelBuild()` [calls the `cancelSiteDeploy`](https://github.com/netlify/build/blob/cb863c1e5019b910e5a675929adc15fd1c7190eb/packages/build/src/error/cancel.js#L20) endpoint. Shouldn't that endpoint result in successful GitHub PR statuses?

This makes more sense to me as well.

This was reported in Netlify community as well: https://community.netlify.com/t/canceling-build-and-pull-request-in-github/16123/2