Flow报错：无法从值位置引用类型`CustomType`的解决咨询

This error pops up when you're trying to use Flow's type identifier CustomType as a runtime value—like passing it as a function argument, assigning it to a variable, or referencing it in runtime logic. Remember: Flow types are only for static type checking; they get stripped out during compilation/runtime and don't exist as actual values in your code.

Here's how to fix this step by step:

1. Ensure CustomType is defined as a pure type (not a value) #

First, double-check your type definition is valid. It should look like this—no class or const declarations, just a type or interface:

/* @flow */
// Correct: Pure type definition for your NoSQL data
type CustomType = {
  id: string,
  fileName: string,
  fileSize?: number,
  [key: string]: mixed, // Allow dynamic properties from NoSQL
};

Avoid mistakes like treating the type as a value (e.g., const myData = CustomType; or fetchData(CustomType)—these will trigger the error).

2. Properly annotate your async function #

When working with your async NoSQL query function, you only need to annotate its return type with CustomType—you don't pass the type into the function itself. Here's an example:

/* @flow */
type CustomType = {
  id: string,
  fileName: string,
  [key: string]: mixed,
};

// Annotate the async function's return type as Promise<CustomType>
async function fetchFileData(fileId: string): Promise<CustomType> {
  // Replace with your actual NoSQL query logic
  const rawData = await db.collection('files').findOne({ id: fileId });
  return rawData;
}

// Usage: Type-check the result, no need to reference CustomType as a value
async function loadFile() {
  const fileData: CustomType = await fetchFileData('file_123');
  console.log(fileData.fileName);
}

3. Handle dynamic properties with runtime type checking (if needed) #

Since your NoSQL data has variable properties depending on the query, you might want to validate the data at runtime. For this, use a type guard function instead of referencing CustomType directly:

/* @flow */
type CustomType = {
  id: string,
  fileName: string,
  [key: string]: mixed,
};

// Runtime type guard to verify data matches CustomType
function isCustomType(data: mixed): data is CustomType {
  return (
    typeof data === 'object' &&
    data !== null &&
    typeof (data as CustomType).id === 'string' &&
    typeof (data as CustomType).fileName === 'string'
  );
}

async function fetchFileData(fileId: string): Promise<CustomType> {
  const rawData = await db.collection('files').findOne({ id: fileId });
  
  if (!isCustomType(rawData)) {
    throw new Error('Invalid data structure returned from NoSQL');
  }
  
  return rawData;
}

Key Takeaway #

Always keep CustomType in the type context (for annotations only) and never use it as a runtime value. If you need to validate data at runtime, build explicit checks with type guards instead of relying on Flow's type definitions.

内容的提问来源于stack exchange，提问作者Micaël Félix