FM / util

/opt/canhelp/node_modules/sucrase/dist/types/util/

/opt/canhelp/node_modules/sucrase/dist/types/util

Name	Size	Mode	Actions
elideImportEquals.d.ts	126	0644	edit dl rm
formatTokens.d.ts	132	0644	edit dl rm
getClassInfo.d.ts	1211	0644	edit dl rm
getDeclarationInfo.d.ts	928	0644	edit dl rm
getIdentifierNames.d.ts	226	0644	edit dl rm
getImportExportSpecifierInfo.d.ts	1133	0644	edit dl rm
getJSXPragmaInfo.d.ts	243	0644	edit dl rm
getNonTypeIdentifiers.d.ts	196	0644	edit dl rm
getTSImportedNames.d.ts	431	0644	edit dl rm
isAsyncOperation.d.ts	655	0644	edit dl rm
isExportFrom.d.ts	280	0644	edit dl rm
isIdentifier.d.ts	306	0644	edit dl rm
removeMaybeImportAttributes.d.ts	253	0644	edit dl rm
shouldElideDefaultExport.d.ts	392	0644	edit dl rm

Edit: /opt/canhelp/node_modules/sucrase/dist/types/util/getImportExportSpecifierInfo.d.ts (1133B)

import type TokenProcessor from "../TokenProcessor";
export type ImportExportSpecifierInfo = {
    isType: false;
    leftName: string;
    rightName: string;
    endIndex: number;
} | {
    isType: true;
    leftName: null;
    rightName: null;
    endIndex: number;
};
/**
 * Determine information about this named import or named export specifier.
 *
 * This syntax is the `a` from statements like these:
 * import {A} from "./foo";
 * export {A};
 * export {A} from "./foo";
 *
 * As it turns out, we can exactly characterize the syntax meaning by simply
 * counting the number of tokens, which can be from 1 to 4:
 * {A}
 * {type A}
 * {A as B}
 * {type A as B}
 *
 * In the type case, we never actually need the names in practice, so don't get
 * them.
 *
 * TODO: There's some redundancy with the type detection here and the isType
 * flag that's already present on tokens in TS mode. This function could
 * potentially be simplified and/or pushed to the call sites to avoid the object
 * allocation.
 */
export default function getImportExportSpecifierInfo(tokens: TokenProcessor, index?: number): ImportExportSpecifierInfo;

cmd: