You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using TypeScript new import type syntax, api-extractor produces Error: Symbol not found for identifier.
If the issue is a bug, how can we reproduce it? Please provide detailed steps and include a GitHub branch if applicable. Your issue will get resolved faster if you can make it easy to investigate.
import type { Export } from './export';
export let x: Export;
Run npm test to see the error -- here is the current output:
api-extractor 7.7.8 - https://api-extractor.com/
Using configuration from [redacted]\api-extractor-bug-import-type\api-extractor.json
Error: Symbol not found for identifier: Export
npm ERR! Test failed. See above for more details.
What is the expected behavior?
Given it's all about type definitions, import type should probably work the same way as normal import.
If this is a bug, please provide the tool version, Node.js version, and OS.
Tool: api-extractor
Tool Version: 7.7.8
Node Version: 10.6.0
Is this a LTS version? Yes
Have you tested on a LTS version? Yes
OS: Windows 10
The text was updated successfully, but these errors were encountered:
Is this a feature or a bug?
Please describe the actual behavior.
When using TypeScript new
import type
syntax, api-extractor producesError: Symbol not found for identifier
.If the issue is a bug, how can we reproduce it? Please provide detailed steps and include a GitHub branch if applicable. Your issue will get resolved faster if you can make it easy to investigate.
See https://github.com/ashmind/api-extractor-bug-import-type to reproduce.
Code looks like this:
Run
npm test
to see the error -- here is the current output:What is the expected behavior?
Given it's all about type definitions,
import type
should probably work the same way as normal import.If this is a bug, please provide the tool version, Node.js version, and OS.
The text was updated successfully, but these errors were encountered: