Nucleus handler tools › Docs › Checks

Newer JavaScript than Nucleus understands

Errores5-onlyA Nucleus check · Nucleus fails: the handler doesn't load, or the session ends.

Why it matters

Nucleus runs handlers with Jint 2.11.58, which only reads ES5 (plus let and const). Arrow functions, template strings, classes, spread and destructuring stop the handler from loading.

Example

✗ Wrong

Game.Play = function () {
  var args = `-width ${Context.Width}`;
};

✓ Right

Game.Play = function () {
  var args = "-width " + Context.Width;
};

How to fix it

Write it the ES5 way: function () {} instead of () =>, "a" + b instead of a template string. The quick fix rewrites most of them.

Turn it off, or change how it shows

Each check can be shown as an error, warning, info or hint, or turned off. VS Code: "splitscreenme.lint.rules": { "es5-only": "off" } in your settings. Notepad++: Plugins › Nucleus Co-op handlers › Settings. Command line: ncdev lint --rule es5-only=off. Other editors: the lint.rules setting of ncdev lsp.

Is this right? Tell us what's wrong
Stuck, or not sure? Ask other handler authors: Discordr/nucleuscoop