The option ignoreNotFoundWarnings: true isn't working for me.
See original GitHub issueDescribe the bug I’m trying to ignore these warnings.

Expected behavior
When I set ignoreNotFoundWarnings: true
to the module options, I expect it to ignore these warnings.
My Workaround My current workaround is to change the regex check to the following:
{
// ...
build: {
warningIgnoreFilters: [
warn =>
warn.name === "ModuleDependencyWarning" &&
/export '.*'( \(reexported as '.*'\))? was not found in/.test(
warn.message
)
];
}
// ...
}
Issue Analytics
- State:
- Created 4 years ago
- Comments:8
Top Results From Across the Web
Property '$auth' does not exist on type Promise - Stack Overflow
This should result in TSC seeing the proper types when using the object now. (By the way, the title is very misleading when...
Read more >nuxt-api-fetch | Explore Tumblr Posts and Blogs - Tumpik
Axios is a promise-based HTTP client that works in the browser and Node.js ... It is true by default but our API does...
Read more >20191224のJavaScriptに関する記事は30件です。
... 'a:not([target="_blank"]):not([href^="#"])' loading: true, ... typescript: { typeCheck: true, ignoreNotFoundWarnings: true } ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@kevinmarrec I’ve upgrade all deps to latest. No longer seeing the error, so I guess it’s working fine. Thank you for following up.
@chanlito Were you saying the regex was just lacking “reexported” check regex check ? Just let me know what are exactly all the warnings that should be ignore but are not, it may be just about the reexport thing.