Automatic checking system gives warning messages of files not in plugin

Devs: Plugins & API
1

I occationally get some warning messages from the auto check about files that are not in my plugin. Could it somehow be that it mixes in code from other plugins in the result?
Here are two such messages. I dont have any corsHelper.ts

Warning

‘response’ is assigned a value but never used.

corsHelper.ts:31

Warning

Unexpected use of ‘fetch’. Use the built-in requestUrl function instead of fetch for network requests in Obsidian.

corsHelper.ts:31

2

I don’t know how exactly the scanner collects files, but a .ts file name with a line number means it saw TypeScript source from somewhere. I’d check three places:

  1. The repo at the scanned tag. git ls-files | grep -i corshelper on that tag. A file tracked in git but never imported (an old folder, a scratch script, a submodule) can still get linted.
  2. Your dependencies. grep -rl corsHelper node_modules. If a package ships its .ts sources and ends up in your bundle, its findings may show up under your plugin.
  3. An inline source map in main.js. Look for sourceMappingURL=data: at the end of the released file. A source map embeds the original sources of everything bundled, dependencies included. Release builds shouldn’t carry one anyway.

Also check which version the report is for. If the file existed in an older release, the warning may come from that scan.

3

Thanks fo answering. Ive searched for those names and the files it pointed to does NOT exist in my plugin code. That is why I wrote the previous message. Anyway, I havent experienced it since then, so hopefully it has passed now.