jQuery.error()?jQuery.error(message) (alias $.error) takes a string and throws an exception containing it (added in jQuery 1.4.1). Plugin authors can override the function for logging or richer display.
jQuery.error(message) → throws (no normal return)
try {
$.error("Missing option");
} catch (err) {
console.log(err.message); // "Missing option"
}
// Official override pattern:
jQuery.error = function (message) {
sendErrorLog("jQuery error: " + message);
throw new Error(message); // still throw!
};| Need | Use |
|---|---|
| Shared plugin throw hook | $.error(msg) |
| Plain app code | throw new Error(msg) |
| Ajax failures | ajaxError / .fail() |
jQuery.error()Pass a message string; catch it if the caller should recover.
jQuery.error("clear message") — execution stops there unless caught.jQuery.error once for app-wide logging.throw new Error(message).| Piece | Required? | Role |
|---|---|---|
message | Yes | String included in the thrown error |
| Return | — | Does not return — throws |
| Override | Optional | Log / display, then throw again |
function error(message):
throw exception with message
// Plugin check:
if options.color is missing:
jQuery.error("spotlight: options.color is required")
// Override (official idea):
jQuery.error = function (message):
sendErrorLog("jQuery error: " + message)
throw new Error(message)Keep these facts handy while throwing plugin errors with jQuery.
| Topic | Detail |
|---|---|
| Syntax | jQuery.error(message) / $.error(message) |
| Since | jQuery 1.4.1 |
| Input | String message |
| Behavior | Throws — no normal return |
| Main use | Overridable hook for plugins |
| Override rule | Log, then still throw |
| Not for Ajax | Use ajax error APIs |
Call $.error (caught for the demo) or run the official override pattern.
Short, copy-ready snippets. Demos catch throws so the editor stays stable.
Call jQuery.error and read err.message in a catch.
try {
jQuery.error("Something went wrong in the plugin");
} catch (err) {
console.log("Caught: " + err.message);
}jQuery.error throws with your string.try/catch stops the exception from becoming uncaught.err.message is the string you passed.catch can still run.Log the message, then throw new Error(message).
jQuery.error = function (message) {
console.log("jQuery error: " + message); // stand-in for sendErrorLog
throw new Error(message);
};
try {
jQuery.error("Logged and rethrown");
} catch (err) {
console.log("caught: " + err.message);
}jQuery.error.throw new Error(message) keeps the API contract.Fail fast when a required option is missing.
$.fn.spotlight = function (options) {
if (!options || !options.color) {
jQuery.error("spotlight: options.color is required");
}
return this.css("color", options.color);
};
try {
$("#t").spotlight({});
} catch (err) {
console.log(err.message);
}jQuery.error stops bad calls early.jQuery.error vs throw new ErrorBoth throw; only jQuery.error is a single overridable hook.
try {
throw new Error("native");
} catch (err) {
console.log(err.message); // "native"
}
try {
jQuery.error("via jQuery.error");
} catch (err) {
console.log(err.message); // "via jQuery.error"
}throw new Error is clear and needs no jQuery.jQuery.error can be replaced once for all plugins.try/catch the same way.$.error.Check these before overriding or calling jQuery.error.
An override that only logs swallows failures. End with throw new Error(message).
Network / HTTP failures belong to ajaxError and .fail() — not $.error.
Without try/catch, the exception surfaces as an uncaught error. Catch when recovery is possible.
throw new Error in appsReserve $.error for the shared plugin hook. Everyday app code is clearer with a native throw.
jQuery.error() is available since jQuery 1.4.1+ in all modern browsers with jQuery loaded. It is a thin throw helper — not a browser API.
Works in Chrome, Firefox, Safari, and Edge whenever jQuery 1.4.1+ is loaded. Prefer throw new Error() in application code unless you need an overridable plugin hook.
Bottom line: Use $.error(msg) as a shared plugin throw hook. Override only if you still throw afterward.
| Approach | Cost | Best for |
|---|---|---|
$.error(msg) | Throw path | Rare validation failures |
throw new Error(msg) | Throw path | App code (clearer) |
| Logging override | I/O bound | Keep logging cheap; never block UI loops |
Throwing is for exceptional cases, not normal control flow. Do not call $.error inside hot loops — validate early and cheaply.
$.error(msg) throws with that message.throw new Error(msg).One line: $.error is a throw helper you can override for logging — but you must still throw.
Learn how jQuery created an isolated copy of itself (legacy API).
8 people found this page helpful