TanTan
e311ca3275
Build NapCat Artifacts / Windows Loader Test (push) Canceled after 0s
Build NapCat Artifacts / Type Check & Test (push) Canceled after 0s
Build NapCat Artifacts / Build NapCat.Framework (push) Canceled after 0s
Build NapCat Artifacts / Build NapCat.Shell (push) Canceled after 0s
37 lines
1.1 KiB
Plaintext
37 lines
1.1 KiB
Plaintext
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;
|