The most recent release of MariaDB Connector/Node.js is: 3.5.4
{% endhint %} [Download](https://mariadb.com/downloads/connectors/connectors-data-access/nodejs-connector) | [Release Notes](/docs/release-notes/connectors/node.js/3.x/3.3.0.md) | [Changelog](/docs/release-notes/connectors/node.js/changelogs/3.x/3.3.0.md) | [Connector/Node.js Overview](/docs/connectors/mariadb-connector-nodejs/mariadb-connector-node-js-guide.md) **Release date:** 21 Mar 2024 MariaDB Connector/Node.js 3.3.0 is a [***Stable***](/docs/release-notes/community-server/about/release-criteria.md) ***(GA)*** release. {% hint style="success" %} **For an overview of MariaDB Connector/Node.js see the** [**About MariaDB Connector/Node.js**](/docs/connectors/mariadb-connector-nodejs/mariadb-connector-node-js-guide.md) **page** {% endhint %} ## Notable changes ### [CONJS-264](https://jira.mariadb.org/browse/CONJS-264) Zero-Configuration SSL In order to have SSL connections, there was 3 solutions: * Have server certificates generated with [trusted node.js Certificate Authorities (CA)](https://ccadb.my.salesforce-sites.com/mozilla/IncludedCACertificateReport), configuration was then like `ssl: true`. * Configure connector with server certificate like:`ssl: { ca: [ fs.readFileSync('server-cert.pem') ] }` * disable certificate ssl verification (not secured!) like:`ssl: { rejectUnauthorized: true }` Since [MariaDB 11.4.1](/docs/release-notes/community-server/11.4/11.4.1.md) ([MDEV-31855](https://jira.mariadb.org/browse/MDEV-31855)), enabling SSL is super easy, with simple configuration like:`ssl: true`, even if server has not configure ssl certificates. The connector doesn't need to know server certificate anymore, if password is not empty. This is part of mission [impossible zero configuration](https://mariadb.org/mission-impossible-zero-configuration-ssl/), client validating ssl certificates using client password. ### [CONJS-284](https://jira.mariadb.org/browse/CONJS-284) pipeline PREPARE and EXECUTE Previous use of connection.execute was executing PREPARE command first, read PREPARE response, then execute EXECUTE command and finally read EXECUTE response. New implementation, when using MariaDB server 10.2+ and with `pipelining` option enable (default value) will execute PREPARE, execute EXECUTE, then only read PREPARE response and read EXECUTE response. This permit to avoid much of the network latency. Benchmarking results using local database:\ (distant database would have even better result)  *This improvement is for first execution of a specific query, since PREPARE is cached by default, second execution would only execute EXECUTE command* ### Other changes * [CONJS-279](https://jira.mariadb.org/browse/CONJS-279) Improve query encoding and decoding performance ## Issues Fixed * [CONJS-281](https://jira.mariadb.org/browse/CONJS-281) cannot connect to 11.3+ server with character-set-collations = utf8mb4=uca1400\_ai\_ci * [CONJS-277](https://jira.mariadb.org/browse/CONJS-277) using connection.importFile when connection is not connected to database result in error * [CONJS-278](https://jira.mariadb.org/browse/CONJS-278) Possible buffer overwrite when sending query bigger than 16M * [CONJS-282](https://jira.mariadb.org/browse/CONJS-282) error when using mysql\_clear\_test password authentication plugin * [CONJS-283](https://jira.mariadb.org/browse/CONJS-283) wrong decoding of binary unsigned MEDIUMINT * [CONJS-285](https://jira.mariadb.org/browse/CONJS-285) DECIMAL field wrong decoding with deprecated option 'supportBigNumbers' set *This page is: Copyright © 2026 MariaDB. All rights reserved.* {% @marketo/form formid="4316" formId="4316" %}