Gajus Kuizinas

Also used this post as sort of sanity validation to ensure that we are not way off-course by adopting this in browser. Seems like not the case.

It is not a dramatic difference, but it would be still nice to address it: ```md with @segment/analytics-next: 555 993 bytes (69% ununsed) without @segment/analytics-next: 445 108 bytes (66% ununsed)...

I don't quite follow. All you need to do is move: ```ts export class AnalyticsBrowser extends AnalyticsBuffered { private _resolveLoadStart: ( settings: AnalyticsBrowserSettings, options: InitOptions ) => void constructor() {...

https://turbo.build/repo/docs/handbook/sharing-code/internal-packages documentation should be updated to reflect that in order to use Internal Packages in a Node.js application (as opposed to Next.js, etc), you have to bundle your Node.js codebase...

> Also, re: @gajus's comment, we've now done that here: https://turbo.build/repo/docs/crafting-your-repository/creating-an-internal-package Can you quote the relevant bit? I fail to find it in the linked document.

Native intertop with signal would make the API a lot nicer to use. Now the API feels awkward: ```ts handle: async ({ signal }) => { const promise = $`sleep...

Updated

Something like this https://github.com/gajus/turbowatch/commit/f9966be788c21c60fb7d12af6c1543e0724449a9

Up to date implementation is here https://github.com/gajus/turbowatch/blob/main/src/killPsTree.ts

Here is a link: https://github.com/gajus/turbowatch/pull/49