@SaidShah had mentioned to me a few weeks ago that the reason the jest-extended matchers do not show up in VS Code/IDE intellisense is due to the **/*.test.ts pattern in the exclude array of our tsconfig file.
Removing that entry and restarting the TS server seems to resolve the issue - VS Code properly detects the extended matchers and provides the appropriate intellisense on hover/typeahead.
This has a side effect of compiling + packaging up our test files with the package which we don't really need. How do we feel about adding a second tsconfig.json which is used for building/packaging the files for publishing? It can extend the base tsconfig that is used for development, with the "exclude": ["**/*.test.ts"], line
@SaidShah had mentioned to me a few weeks ago that the reason the
jest-extendedmatchers do not show up in VS Code/IDE intellisense is due to the**/*.test.tspattern in theexcludearray of ourtsconfigfile.Removing that entry and restarting the TS server seems to resolve the issue - VS Code properly detects the extended matchers and provides the appropriate intellisense on hover/typeahead.
This has a side effect of compiling + packaging up our test files with the package which we don't really need. How do we feel about adding a second tsconfig.json which is used for building/packaging the files for publishing? It can extend the base tsconfig that is used for development, with the
"exclude": ["**/*.test.ts"],line