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.4.0.md) | [Changelog](/docs/release-notes/connectors/node.js/changelogs/3.x/3.4.0.md) | [Connector/Node.js Overview](/docs/connectors/mariadb-connector-nodejs/mariadb-connector-node-js-guide.md) **Release date:** 24 Oct 2024 MariaDB Connector/Node.js 3.4.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-299](https://jira.mariadb.org/browse/CONJS-299) Support of the PARSEC Authentication Plugin which is provided starting with MariaDB Server 11.6. See the [PARSEC Authentication Plugin documentation](/docs/server/reference/plugins/authentication-plugins/authentication-plugin-parsec.md) for more details * [CONJS-295](https://jira.mariadb.org/browse/CONJS-295) A new option jsonStrings has been added which can be used to return a JSON field as type string instead of type JSON When working with JSON fields in MariaDB and MySQL, it's important to note that the handling differs between the two database systems. * autoJsonMap Option: The autoJsonMap option provides flexibility in MariaDB. You can choose to have the connector return either JSON objects or string representations of the JSON data. * jsonStrings Option: The jsonStrings option introduces a similar choice for MySQL JSON fields. It allows you to specify whether the connector should return JSON objects or string values. In essence, the JSON fields will be returned either as a JSON or String will depend on 2 different options depending on the database you’re working with. * [CONJS-296](https://jira.mariadb.org/browse/CONJS-296) Add option enableKeepAlive / keepAliveInitialDelay alias for keepAliveDelay for mysql2 compatibility The *keepAliveDelay* option in MariaDB connectors controls the frequency of keep-alive packets sent to maintain a persistent connection. * Disabled: When set to 0, keep-alive functionality is disabled. * Enabled: For any non-zero value, keep-alive packets are sent at the specified interval. MySQL 2 Compatibility:\ To ensure compatibility with the MySQL 2 connector, the *enableKeepAlive* and *keepAliveInitialDelay* options have been added. * enableKeepAlive: If disabled, keepAliveDelay is automatically set to 0, effectively disabling keep-alive. * enableKeepAlive: If enabled, keepAliveDelay is set to the value specified in keepAliveInitialDelay. In summary, the *keepAliveDelay* option determines the keep-alive frequency, while the *enableKeepAlive* and *keepAliveInitialDelay* options provide compatibility with MySQL 2 connectors by allowing you to control whether keep-alive is enabled and set the initial delay. ## Issues Fixed [CONJS-303](https://jira.mariadb.org/browse/CONJS-303) DMLs are not returning an output while streaming *This page is: Copyright © 2026 MariaDB. All rights reserved.* {% @marketo/form formid="4316" formId="4316" %}