What problem does it solve? Adding the MariaDB Connector/Node.js to a project involves subtle decisions that are easy to get wrong: which API entry point to import, whether native build tools are needed, how TLS verification behaves, and what pool defaults apply. This Skill prevents common misconfigurations such as adding node-gyp to Dockerfiles, installing a nonexistent @types package, or disabling certificate verification unnecessarily. ## Core Features & Use Cases - Correct installation guidance: Confirms the mariadb npm package is pure JavaScript with no native build step, requires Node.js 20 or later on the 3.5 line, and bundles its own TypeScript typings. - Entry point and API selection: Explains that the promise API is the default export, the callback API lives behind the mariadb/callback subpath, and deep lib/ imports are blocked by the exports map. - TLS and pooling configuration: Covers ssl: true verification against public CAs and MariaDB 11.4+ zero-configuration TLS, private CA and mutual TLS object forms, and pool defaults (connectionLimit 10, acquireTimeout 10000 ms, idleTimeout 1800 s). - Use Case: You are containerizing a Node.js service that talks to MariaDB. Use this Skill to write a minimal Dockerfile without build tools, connect over TLS with a private CA, and configure a connection pool with coherent timeouts. ## Quick Start Install and configure the MariaDB Connector/Node.js in my Node.js 20 project with TLS and a connection pool.
