moo-server (MooTools for Node.js)

Common errors

• ReferenceError: require is not defined in ES module scope

  cause Attempting to use `require()` in a JavaScript file that is treated as an ES module (e.g., due to `"type": "module"` in `package.json` or a `.mjs` file extension).
  fix This package is CommonJS-only. Either revert your project to CommonJS (remove `"type": "module"`, use `.js` files), or, preferably, migrate to a modern library that supports ESM.

• TypeError: Object.prototype.someMethod is not a function (or similar prototype-related error)

  cause A utility method expected from `moo-server` (which might augment prototypes) is not found, typically because the package failed to load or the Node.js version is too new to support its internal mechanisms.
  fix This error indicates `moo-server` is either not loaded correctly or its prototype extensions are not compatible with your Node.js runtime. This package is abandoned and incompatible with modern systems; replacement is the only viable fix.

• Error: Cannot find module 'moo-server'

  cause The package failed to install correctly, or npm/yarn is unable to resolve it from the registry due to its age, deprecated status, or incompatibility with modern package managers.
  fix Verify the package exists on npm (it may have been unpublished or deprecated). Even if found, installation on modern systems is problematic. Do not attempt to use this package; it is fundamentally unsupported.

• SyntaxError: Unexpected token '.' (or similar low-level JavaScript syntax error)

  cause Running the `moo-server` package or code relying on it in a modern Node.js environment, where its ancient JavaScript syntax (e.g., old keywords, lack of strict mode compliance) is no longer valid or conflicts with newer language features.
  fix This package uses very old JavaScript syntax and APIs. It is fundamentally incompatible with modern Node.js. Downgrading Node.js is not recommended for security reasons; replace the package with a contemporary alternative.

Warnings

• breaking This package is entirely incompatible with modern Node.js versions (e.g., v12+). It was developed for Node.js v0.4.10 and earlier, making it highly unlikely to run without severe errors or crashing on newer runtimes.
  Fix: Do not use this package in any new or existing project. Migrate any legacy code away from it to actively maintained solutions.
• breaking The `moo-server` package uses CommonJS `require()` exclusively. It does not support ES Modules (`import/export`) syntax, and attempting to use it in an ESM context will result in syntax errors.
  Fix: This package cannot be made compatible with ESM. Avoid using it; if strictly necessary for legacy reasons, ensure your project exclusively uses CommonJS and an ancient Node.js runtime.
• gotcha This package is completely abandoned and has not been updated for over a decade. It likely contains numerous unpatched security vulnerabilities, making it extremely risky for use in any production or sensitive environment.
  Fix: Immediately cease use of this package. There is no fix for its security posture short of complete replacement with a modern, secure library.
• gotcha Like many libraries from its era (including client-side MooTools), `moo-server` may aggressively extend built-in JavaScript prototypes (e.g., `Object.prototype`, `Array.prototype`), leading to unexpected behavior, conflicts with other libraries, and difficult-to-debug issues.
  Fix: Avoid prototype pollution by not using this package. If forced to use it, isolate its usage and be aware of potential global side-effects, which are considered bad practice in modern JavaScript.
• gotcha There is no TypeScript support (type definitions) available for `moo-server`. Using it in a TypeScript project would require manually declaring its types as `any` or creating custom declaration files, which is not recommended given its abandonment and insecurity.
  Fix: Migrate to a modern, actively maintained library with robust TypeScript support.

Install

• npm install moo-server npm
• yarn add moo-server yarn
• pnpm add moo-server pnpm

Imports

• mooServer
  wrong:

  import mooServer from 'moo-server';

  correct:

  const mooServer = require('moo-server');

  This package strictly uses CommonJS `require()` syntax. ESM imports are not supported and will cause syntax errors.
• MooServerUtilities
  wrong:

  import { someMethod } from 'moo-server';

  correct:

  const MooServerUtilities = require('moo-server');
  // Access utilities like MooServerUtilities.someMethod()

  It's highly probable the package exports a single object containing all its utilities, rather than named exports, typical of older CommonJS modules.
• GlobalAugmentation
  wrong:

  import 'moo-server';

  correct:

  require('moo-server');
  // Globals or prototypes might be augmented after this line

  Some extremely old libraries, including parts of MooTools, would augment global objects or prototypes as a side effect of `require()`. There might not be a direct return value from the `require()` call itself if its primary function is global side-effects.

Quickstart

Demonstrates how to import and hypothetically use the `moo-server` package with CommonJS in an extremely old Node.js environment, showcasing its historical context and incompatibility with modern systems.

// This example is for historical context only and requires an extremely old Node.js environment
// (specifically Node.js v0.4.10 to ~v0.6.x) to function correctly, if at all. 
// It is not recommended for modern development.

const http = require('http');
const mooServer = require('moo-server'); // Assuming it returns an object of utilities

// In an actual scenario from its era, moo-server might extend prototypes or provide utilities.
// This is a hypothetical usage pattern demonstrating CommonJS and old Node.js.
// For instance, MooTools heavily extended Array.prototype, Function.prototype, etc.
// A server-side version might offer similar extensions or standalone utilities.

// Hypothetical utility provided by moo-server (purely illustrative)
if (mooServer && typeof mooServer.capitalize === 'function') {
  console.log("MooServer loaded successfully.");
  console.log("Example utility call: ", mooServer.capitalize("hello world"));
} else {
  console.log("MooServer might have augmented globals or simply loaded without a direct export on this (old) Node.js version.");
}

const server = http.createServer(function (req, res) {
  res.writeHead(200, {'Content-Type': 'text/plain'});
  res.end('Hello from moo-server era Node.js!\n');
});

server.listen(3000, '127.0.0.1');
console.log('Server running at http://127.0.0.1:3000/');
console.log('To run this, you would need to use a Node.js version manager (like nvm) to install an old Node.js version, e.g., v0.6.0.');