/home/techb158/balavpn.abdallabala.com/node_modules/eslint/messages
NameSizeModeActions
all-files-ignored.js6600666editdlrm
all-matched-files-ignored.js10250666editdlrm
config-file-missing.js5260666editdlrm
config-plugin-missing.js4450666editdlrm
config-serialize-function.js9420666editdlrm
eslintrc-incompat.js52310666editdlrm
eslintrc-plugins.js9320666editdlrm
extend-config-missing.js4180666editdlrm
failed-to-read-json.js1570666editdlrm
file-not-found.js2680666editdlrm
invalid-rule-options.js6480666editdlrm
invalid-rule-severity.js4080666editdlrm
no-config-found.js5270666editdlrm
plugin-conflict.js5180666editdlrm
plugin-invalid.js6530666editdlrm
plugin-missing.js6590666editdlrm
print-config-with-directory-path.js2520666editdlrm
shared.js5460666editdlrm
whitespace-found.js3860666editdlrm
Edit: /home/techb158/balavpn.abdallabala.com/node_modules/eslint/messages/config-serialize-function.js (942B)
"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(); };