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
I鈥檓 testing console-fail-test in one of our projects within our monorepo.
Our Vitest env is configured using a single vitest.config file pointing to a setupTest.ts file inside each monorepo project, so I can鈥檛 change the shared vitest config, because it will affect all projects.
Note that my setupTest.ts is a TS file, so when I鈥檓 importing console-fail-test TS is complaining about missing declaration types for this package:
As a workaround I had to add a couple of TS and Eslint ignores to bypass this issue:
// setupTest.ts// @ts-expect-error console-fail-test is not exporting typesimport{cft}from"console-fail-test";// eslint-disable-next-line @typescript-eslint/no-unsafe-callcft();
Additional Info
No response
The text was updated successfully, but these errors were encountered:
馃 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 馃挋
Adds @joel-daros as a contributor for ideas.
This was requested by JoshuaKGoldberg [in this
comment](#531 (comment))
---------
Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
Bug Report Checklist
main
branch of the repository.Overview
I鈥檓 testing
console-fail-test
in one of our projects within our monorepo.Our Vitest env is configured using a single
vitest.config
file pointing to asetupTest.ts
file inside each monorepo project, so I can鈥檛 change the shared vitest config, because it will affect all projects.Note that my
setupTest.ts
is a TS file, so when I鈥檓 importingconsole-fail-test
TS is complaining about missing declaration types for this package:As a workaround I had to add a couple of TS and Eslint ignores to bypass this issue:
Additional Info
No response
The text was updated successfully, but these errors were encountered: