DMleadgen
46d973904b
Next.js website for Rocky Mountain Vending company featuring: - Product catalog with Stripe integration - Service areas and parts pages - Admin dashboard with Clerk authentication - SEO optimized pages with JSON-LD structured data Co-authored-by: Cursor <cursoragent@cursor.com>
46 lines
2.3 KiB
Text
46 lines
2.3 KiB
Text
import * as CPUProfile from '../../cpu_profile/cpu_profile.js';
|
|
import * as Helpers from '../helpers/helpers.js';
|
|
import * as Types from '../types/types.js';
|
|
declare const profilesInProcess: Map<Types.Events.ProcessID, Map<Types.Events.ThreadID, ProfileData>>;
|
|
declare const entryToNode: Map<Types.Events.Event, Helpers.TreeHelpers.TraceEntryNode>;
|
|
export declare function reset(): void;
|
|
export declare function handleEvent(event: Types.Events.Event): void;
|
|
export declare function finalize(parseOptions?: Types.Configuration.ParseOptions): Promise<void>;
|
|
export declare function data(): SamplesHandlerData;
|
|
export interface SamplesHandlerData {
|
|
profilesInProcess: typeof profilesInProcess;
|
|
entryToNode: typeof entryToNode;
|
|
}
|
|
export interface ProfileData {
|
|
profileId: Types.Events.ProfileID;
|
|
rawProfile: CPUProfile.CPUProfileDataModel.ExtendedProfile;
|
|
parsedProfile: CPUProfile.CPUProfileDataModel.CPUProfileDataModel;
|
|
/**
|
|
* Contains the calls built from the CPU profile samples.
|
|
* Note: This doesn't contain real trace events coming from the
|
|
* browser, only calls synthetically typed as trace events for
|
|
* compatibility, as such it only makes sense to use them in pure CPU
|
|
* profiles.
|
|
*
|
|
* If you need the profile calls from a CPU profile obtained from a
|
|
* web trace, use the data exported by the RendererHandler instead.
|
|
*/
|
|
profileCalls: Types.Events.SyntheticProfileCall[];
|
|
/**
|
|
* Contains the call tree built from the CPU profile samples.
|
|
* Similar to the profileCalls field, this tree does not contain nor
|
|
* take into account trace events, as such it only makes sense to use
|
|
* them in pure CPU profiles.
|
|
*/
|
|
profileTree?: Helpers.TreeHelpers.TraceEntryTree;
|
|
}
|
|
/**
|
|
* Returns the name of a function for a given synthetic profile call.
|
|
* We first look to find the ProfileNode representing this call, and use its
|
|
* function name. This is preferred (and should always exist) because if we
|
|
* resolve sourcemaps, we will update this name. If that name is not present,
|
|
* we fall back to the function name that was in the callframe that we got
|
|
* when parsing the profile's trace data.
|
|
*/
|
|
export declare function getProfileCallFunctionName(data: SamplesHandlerData, entry: Types.Events.SyntheticProfileCall): string;
|
|
export {};
|