Handling Remote Import Failures in cspell Configuration Files

[jcommuri]

I'm encountering an issue with cspell when using the import field in the configuration file to reference a remote file hosted on Artifactory.

If the remote file is inaccessible (e.g., due to no internet or Artifactory being down), cspell throws an error and stops execution entirely — even if a local fallback configuration is specified earlier in the import array.

{ "version": "0.2", "import": [ "./local-cspell.json", "https://my-artifactory.com/artifactory/dev-local/public/cspell.json" ], "words": ["customword2"], "flagWords": ["hte"] }

Questions:

1. Is there a way to configure cspell to gracefully handle remote import failures and continue with the next file in the import array or use default set of words ?
2. If not, are there any plans to add remote import error handling in future versions?
3. Any recommended workarounds to ensure cspell can still run even when the remote config is inaccessible?

Thank you for your help!

[Jason3S]

@jcommuri,

Does the --no-exit-code option work for you?

[jcommuri]

This doesn’t work when used with pre-commit hooks, as the step always passes, which is undesirable.

[Jason3S]

I have added a new option: --continue-on-error.

Note: it will still have an exit code of 1.