hatch-surf/node_modules/eslint/messages/config-serialize-function.js
Riley Zhang df378d33ef
Some checks failed
CI / go (push) Waiting to run
CI / docker (push) Waiting to run
CI / lint-go (push) Waiting to run
CI / lint-docs (push) Waiting to run
CI / check-paperclip (push) Waiting to run
Deploy static site / Deploy to GitHub Pages (push) Has been cancelled
Deploy static site / Deploy via Docker to hatch.surf (push) Has been cancelled
Merge GitHub main into Gitea repo (allow unrelated histories)
Resolved conflicts by taking GitHub versions for:
- .dockerignore, .gitignore, Dockerfile, README.md, docker-compose.yml

Kept deploy.sh updated to:
- Pull from GitHub (primary source)
- Push to Gitea (push-mirror)
- Build from site/ directory (GitHub structure)

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-06-25 05:20:46 +02:00

31 lines
942 B
JavaScript

"use strict";
module.exports = function ({ key, objectKey }) {
// special case for parsers
const isParser =
objectKey === "parser" && (key === "parse" || key === "parseForESLint");
const parserMessage = `
This typically happens when you're using a custom parser that does not
provide a "meta" property, which is how ESLint determines the serialized
representation. Please open an issue with the maintainer of the custom parser
and share this link:
https://eslint.org/docs/latest/extend/custom-parsers#meta-data-in-custom-parsers
`.trim();
return `
The requested operation requires ESLint to serialize configuration data,
but the configuration key "${objectKey}.${key}" contains a function value,
which cannot be serialized.
${
isParser
? parserMessage
: "Please double-check your configuration for errors."
}
If you still have problems, please stop by https://eslint.org/chat/help to chat
with the team.
`.trimStart();
};