--incremental errors

[Jojoshua]

Describe the bug

I have been using svelte 5 + webpack for a long time with no issue. I tested out trying sv-check with --incremental and now I am getting a bunch of these errors. I have put my config in the svelte-loader. Is svelte.config.js necessary?

No svelte.config.js found. Using https://github.com/sveltejs/svelte-preprocess as fallback

Reproduction

Bundling as shown here https://github.com/sveltejs/svelte-loader#readme

Expected behaviour

No errors shown

System Info

• OS: [e.g. Windows]
• IDE: [e.g. VSCode, Atom]

Which package is the issue about?

No response

Additional Information, eg. Screenshots

No response

[jasonlyu123]

This doesn't sound right. The log you mentioned should be editor-only and not exist in svelte-check. Can you provide a reproduction?

svelte.config.js is optional to some degree. There will be a fallback if you don't have it, but it might not work the same as your preprocessor setting in another file. The log is a verbose logging for the potential difference. We won't read the config from your webpack config. You can configure webpack in various ways, so it'll be hard to support this.

[Jojoshua]

I'm having a hard time getting a clean repro. I see this message about 20 times in a row so it might be one of the files it's seeing. I have a mixture of svelte and svelte.ts files. I don't think webpack is in play here because just running svelte-check --incremental is enough to cause it. I may need to dig around in svelte-check source to help figure out how to reproduce.

[Jojoshua]

Maybe this statement assumes that it can pull a file from github? My environment has github blocked

In any case, I created a svelte.config.mjs file with a contents below and the error message is now gone. Can svelte-check just handle this internally?

const config = {};
export default config;

[jasonlyu123]

No. It is't loading from GitHub or npm. It's loading from your node_modules. As I mentioned, it's not an error but rather verbose logging to help people debug why the preprocessor setup differs. You're probably hitting a case where the log level isn't set up correctly.

[Jojoshua]

That makes sense. It was acting like an error in my CI build. How do I set svelte check to not write out verbose?

[Jojoshua]

I tested with --threshold error and still getting these messages