Typescript & JavaScript support
We support various import statements, including require.
Import statements
Here's a non-exhaustive list of the variations we support.
Supported project configurations
tsconfig.json
tsconfig.json
Used fields
compilerOptions.paths
for resolving extracted module import pathsextends
for mergingcompilerOptions.paths
from multiple files
package.json
package.json
dependencies
anddevDependencies
are read and used to filter 3rd party library dependencies out of the extracted imports, optimising the analysis
Known problems ❌
❌ Import statements that are using variables in the path of the module cannot be resolved as the code is never executed.
Workaround: Use dependencies.json
to mitigate critical blindspots.
❌ Package.json import aliases are not supported. Workaround: Use
dependencies.json
to mitigate critical blindspots.❌
fetch()
and similar calls to APIs or URLs are not automatically mapped to modules. Workaround: Usedependencies.json
to mitigate critical blindspots.
Supported frameworks
.tsx
and .jsx
files are by default assumed to be TypeScript/JavaScript files and are included in the processing. They are further considered as User flow test cases
by default. If a framework is specified here, it means at least one project built with that framework is part of the quality assurance activities of that language, and has been deemed correctly extracted.
React
.tsx
and .jsx
support
SolidJS
.tsx
and .jsx
support
VueJS
.vue
files are treated as TypeScript/JavaScript files and go through the same extraction. .vue
files are also considered as User flow test cases
by default.
Last updated