chore: update to v0.10.2 (#114)

Author: pffigueiredo

CHANGELOG.md

@@ -1,6 +1,6 @@
-## UNRELEASED
+## 0.10.2 (2024-11-05)
 
-expose types property on public HTTPQueryOptions type
+Expose `types` property on public HTTPQueryOptions type
 
 ## 0.10.1 (2024-10-07)
 

CONFIG.md

@@ -108,6 +108,29 @@ const rows = await sql('SELECT * FROM posts WHERE id = $1', [postId], {
 clearTimeout(timeout);
 ```
 
+### `types: typeof PgTypes`
+
+The `types` option can be passed to `neon(...)` to override the default PostgreSQL type parsers provided by `PgTypes`. This is useful if you want to define custom parsing behavior for specific PostgreSQL data types, allowing you to control how data is converted when retrieved from the database. Learn more in the [PgTypes official documentation](https://github.com/brianc/node-pg-types).
+
+Example of usage:
+
+```typescript
+import PgTypes from 'pg-types';
+import { neon } from '@neondatabase/serverless';
+
+// Define custom parsers for specific PostgreSQL types
+// Parse PostgreSQL `DATE` fields as JavaScript `Date` objects
+PgTypes.setTypeParser(PgTypes.builtins.DATE, (val) => new Date(val));
+
+// Parse PostgreSQL `NUMERIC` fields as JavaScript `float` values
+PgTypes.setTypeParser(PgTypes.builtins.NUMERIC, parseFloat);
+
+// Configure the Neon client with the custom `types` parser
+const sql = neon(process.env.DATABASE_URL, {
+  types: PgTypes, // Pass in the custom PgTypes object here
+});
+```
+
 ### `authToken: string | (() => Promise<string> | string)`
 
 The `authToken` option can be passed to `neon(...)` to set the `Authorization` header for the `fetch` request. This allows you to authenticate database requests against third-party authentication providers. So, this mechanism can be used to ensure that access control and authorization are managed effectively across different systems.

dist/jsr/jsr.json

@@ -1,6 +1,6 @@
 {
   "name": "@neon/serverless",
-  "version": "0.10.1",
+  "version": "0.10.2",
   "exports": "./index.js",
   "imports": {
     "pg": "npm:@types/pg@8.11.6"

dist/npm/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 0.10.2 (2024-11-05)
+
+Expose `types` property on public HTTPQueryOptions type
+
 ## 0.10.1 (2024-10-07)
 
 Fix `CONFIG.MD` documentation.

dist/npm/CONFIG.md

@@ -108,6 +108,29 @@ const rows = await sql('SELECT * FROM posts WHERE id = $1', [postId], {
 clearTimeout(timeout);
 ```
 
+### `types: typeof PgTypes`
+
+The `types` option can be passed to `neon(...)` to override the default PostgreSQL type parsers provided by `PgTypes`. This is useful if you want to define custom parsing behavior for specific PostgreSQL data types, allowing you to control how data is converted when retrieved from the database. Learn more in the [PgTypes official documentation](https://github.com/brianc/node-pg-types).
+
+Example of usage:
+
+```typescript
+import PgTypes from 'pg-types';
+import { neon } from '@neondatabase/serverless';
+
+// Define custom parsers for specific PostgreSQL types
+// Parse PostgreSQL `DATE` fields as JavaScript `Date` objects
+PgTypes.setTypeParser(PgTypes.builtins.DATE, (val) => new Date(val));
+
+// Parse PostgreSQL `NUMERIC` fields as JavaScript `float` values
+PgTypes.setTypeParser(PgTypes.builtins.NUMERIC, parseFloat);
+
+// Configure the Neon client with the custom `types` parser
+const sql = neon(process.env.DATABASE_URL, {
+  types: PgTypes, // Pass in the custom PgTypes object here
+});
+```
+
 ### `authToken: string | (() => Promise<string> | string)`
 
 The `authToken` option can be passed to `neon(...)` to set the `Authorization` header for the `fetch` request. This allows you to authenticate database requests against third-party authentication providers. So, this mechanism can be used to ensure that access control and authorization are managed effectively across different systems.

dist/npm/package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@neondatabase/serverless",
-  "version": "0.10.1",
+  "version": "0.10.2",
   "author": "Neon",
   "description": "node-postgres for serverless environments from neon.tech",
   "exports": {