I renewed my license, and now I'm getting build warnings.

[mrkos67]

Quick, short summary:
I renewed my license and now my project build yields "No Source Code to Show" warnings on several files located in a JS library folder that's symlink'ed into my project's root folder.

Expected results:
Project builds without warnings.

Actual results:
Upon build, I get the following warning on several files that I use from a JS library folder of my own making, shared between projects, that has been symlink'ed into my project root:

[No Source Code To Show]

File ignored because of a matching ignore pattern. Use "--no-ignore" to disable file ignore settings or
use "--no-warn-ignored" to suppress this warning.

Google searching for codekit "no source code to show" yields no results.

When I deleted the symlink'ed and try to build, I get the following errors:

ESLint failed to run with this error:
Oops! Something went wrong! :(

ESLint: 9.0.0

No files matching the pattern "/Users/johnbandy/Work/Projects/Active/CNCT/Vidbot-V2/_ConcatJS/src/
utils/Numbers.js" were found.
Please check for typing mistakes in the pattern.

Bundling failed with this error: Could not resolve "../../_ConcatJS/src/utils/Dates.js" from "core/Vidbot.js"

Obviously, since I import these files using the symlink pathway into my root folder.

Exact steps to reproduce:
Not sure since this started after I renewed my license.

A link to download a simplified project or file that shows the issue:
n/a

Your configuration (any details about your system that you think might be relevant)
I'm running Codekit v3.25 build 34576, if this helps.

[bdkjones]

Yea. The symlink is very likely the cause—not all of the tooling in CodeKit supports Symlinks, so the app skips them entirely when indexing.

If you want to share some JS files across multiple projects, the CodeKit Frameworks feature was designed to do exactly that. Check out the docs for it at codekitapp.com/help/

[mrkos67]

So then why was all of this working perfectly before and now that I've renewed my license, I'm getting these warnings? Or, how do I use the '--no-ignore' or '--no-warn-ignore' flags, cuz I don't see either of those options in the ESLint settings?

[bdkjones]

It has nothing to do with the license. It's because you updated to a version of CodeKit that has ESLint 9.x and ESLint 9.x...made some choices. I originally left this in place because the warning is trying to tell you something: "I didn't check this file over here, so there may be problems in it. You're on your own."

But it seems like people would prefer silent failure rather than deal with resolving the configuration.

[mrkos67]

How do I "resolve the configuration" then and ignore these files in the new ESLint from within Codekit?

[bdkjones]

Don't use symlinks. I'll push an update tomorrow hopefully to silence the warnings.