neo4j-driver 5.9.0 → 5.9.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/lib/browser/neo4j-web.esm.js +247 -140
- package/lib/browser/neo4j-web.esm.min.js +1 -1
- package/lib/browser/neo4j-web.js +247 -140
- package/lib/browser/neo4j-web.min.js +1 -1
- package/lib/index.js +2 -127
- package/lib/version.js +1 -1
- package/package.json +4 -4
package/lib/index.js
CHANGED
|
@@ -147,141 +147,16 @@ function createAuthManager(authTokenOrManager) {
|
|
|
147
147
|
* Construct a new Neo4j Driver. This is your main entry point for this
|
|
148
148
|
* library.
|
|
149
149
|
*
|
|
150
|
-
* ## Configuration
|
|
151
|
-
*
|
|
152
|
-
* This function optionally takes a configuration argument. Available configuration
|
|
153
|
-
* options are as follows:
|
|
154
|
-
*
|
|
155
|
-
* {
|
|
156
|
-
* // Encryption level: ENCRYPTION_ON or ENCRYPTION_OFF.
|
|
157
|
-
* encrypted: ENCRYPTION_ON|ENCRYPTION_OFF
|
|
158
|
-
*
|
|
159
|
-
* // Trust strategy to use if encryption is enabled. There is no mode to disable
|
|
160
|
-
* // trust other than disabling encryption altogether. The reason for
|
|
161
|
-
* // this is that if you don't know who you are talking to, it is easy for an
|
|
162
|
-
* // attacker to hijack your encrypted connection, rendering encryption pointless.
|
|
163
|
-
* //
|
|
164
|
-
* // TRUST_SYSTEM_CA_SIGNED_CERTIFICATES is the default choice. For NodeJS environments, this
|
|
165
|
-
* // means that you trust whatever certificates are in the default trusted certificate
|
|
166
|
-
* // store of the underlying system. For Browser environments, the trusted certificate
|
|
167
|
-
* // store is usually managed by the browser. Refer to your system or browser documentation
|
|
168
|
-
* // if you want to explicitly add a certificate as trusted.
|
|
169
|
-
* //
|
|
170
|
-
* // TRUST_CUSTOM_CA_SIGNED_CERTIFICATES is another option for trust verification -
|
|
171
|
-
* // whenever we establish an encrypted connection, we ensure the host is using
|
|
172
|
-
* // an encryption certificate that is in, or is signed by, a certificate given
|
|
173
|
-
* // as trusted through configuration. This option is only available for NodeJS environments.
|
|
174
|
-
* //
|
|
175
|
-
* // TRUST_ALL_CERTIFICATES means that you trust everything without any verifications
|
|
176
|
-
* // steps carried out. This option is only available for NodeJS environments and should not
|
|
177
|
-
* // be used on production systems.
|
|
178
|
-
* trust: "TRUST_SYSTEM_CA_SIGNED_CERTIFICATES" | "TRUST_CUSTOM_CA_SIGNED_CERTIFICATES" |
|
|
179
|
-
* "TRUST_ALL_CERTIFICATES",
|
|
180
|
-
*
|
|
181
|
-
* // List of one or more paths to trusted encryption certificates. This only
|
|
182
|
-
* // works in the NodeJS bundle, and only matters if you use "TRUST_CUSTOM_CA_SIGNED_CERTIFICATES".
|
|
183
|
-
* // The certificate files should be in regular X.509 PEM format.
|
|
184
|
-
* // For instance, ['./trusted.pem']
|
|
185
|
-
* trustedCertificates: [],
|
|
186
|
-
*
|
|
187
|
-
* // The maximum total number of connections allowed to be managed by the connection pool, per host.
|
|
188
|
-
* // This includes both in-use and idle connections. No maximum connection pool size is imposed
|
|
189
|
-
* // by default.
|
|
190
|
-
* maxConnectionPoolSize: 100,
|
|
191
|
-
*
|
|
192
|
-
* // The maximum allowed lifetime for a pooled connection in milliseconds. Pooled connections older than this
|
|
193
|
-
* // threshold will be closed and removed from the pool. Such discarding happens during connection acquisition
|
|
194
|
-
* // so that new session is never backed by an old connection. Setting this option to a low value will cause
|
|
195
|
-
* // a high connection churn and might result in a performance hit. It is recommended to set maximum lifetime
|
|
196
|
-
* // to a slightly smaller value than the one configured in network equipment (load balancer, proxy, firewall,
|
|
197
|
-
* // etc. can also limit maximum connection lifetime). No maximum lifetime limit is imposed by default. Zero
|
|
198
|
-
* // and negative values result in lifetime not being checked.
|
|
199
|
-
* maxConnectionLifetime: 60 * 60 * 1000, // 1 hour
|
|
200
|
-
*
|
|
201
|
-
* // The maximum amount of time to wait to acquire a connection from the pool (to either create a new
|
|
202
|
-
* // connection or borrow an existing one.
|
|
203
|
-
* connectionAcquisitionTimeout: 60000, // 1 minute
|
|
204
|
-
*
|
|
205
|
-
* // Specify the maximum time in milliseconds transactions are allowed to retry via
|
|
206
|
-
* // `Session#executeRead()` and `Session#executeWrite()` functions.
|
|
207
|
-
* // These functions will retry the given unit of work on `ServiceUnavailable`, `SessionExpired` and transient
|
|
208
|
-
* // errors with exponential backoff using initial delay of 1 second.
|
|
209
|
-
* // Default value is 30000 which is 30 seconds.
|
|
210
|
-
* maxTransactionRetryTime: 30000, // 30 seconds
|
|
211
|
-
*
|
|
212
|
-
* // Specify socket connection timeout in milliseconds. Numeric values are expected. Negative and zero values
|
|
213
|
-
* // result in no timeout being applied. Connection establishment will be then bound by the timeout configured
|
|
214
|
-
* // on the operating system level. Default value is 30000, which is 30 seconds.
|
|
215
|
-
* connectionTimeout: 30000, // 30 seconds
|
|
216
|
-
*
|
|
217
|
-
* // Make this driver always return native JavaScript numbers for integer values, instead of the
|
|
218
|
-
* // dedicated {@link Integer} class. Values that do not fit in native number bit range will be represented as
|
|
219
|
-
* // `Number.NEGATIVE_INFINITY` or `Number.POSITIVE_INFINITY`.
|
|
220
|
-
* // **Warning:** ResultSummary It is not always safe to enable this setting when JavaScript applications are not the only ones
|
|
221
|
-
* // interacting with the database. Stored numbers might in such case be not representable by native
|
|
222
|
-
* // {@link Number} type and thus driver will return lossy values. This might also happen when data was
|
|
223
|
-
* // initially imported using neo4j import tool and contained numbers larger than
|
|
224
|
-
* // `Number.MAX_SAFE_INTEGER`. Driver will then return positive infinity, which is lossy.
|
|
225
|
-
* // Default value for this option is `false` because native JavaScript numbers might result
|
|
226
|
-
* // in loss of precision in the general case.
|
|
227
|
-
* disableLosslessIntegers: false,
|
|
228
|
-
*
|
|
229
|
-
* // Make this driver always return native Javascript {@link BigInt} for integer values, instead of the dedicated {@link Integer} class or {@link Number}.
|
|
230
|
-
* //
|
|
231
|
-
* // Default value for this option is `false` for backwards compatibility.
|
|
232
|
-
* //
|
|
233
|
-
* // **Warning:** `BigInt` doesn't implement the method `toJSON`. In maner of serialize it as `json`, It's needed to add a custom implementation of the `toJSON` on the
|
|
234
|
-
* // `BigInt.prototype` {@see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt#use_within_json}
|
|
235
|
-
* useBigInt: false,
|
|
236
|
-
*
|
|
237
|
-
* // Specify the logging configuration for the driver. Object should have two properties `level` and `logger`.
|
|
238
|
-
* //
|
|
239
|
-
* // Property `level` represents the logging level which should be one of: 'error', 'warn', 'info' or 'debug'. This property is optional and
|
|
240
|
-
* // its default value is 'info'. Levels have priorities: 'error': 0, 'warn': 1, 'info': 2, 'debug': 3. Enabling a certain level also enables all
|
|
241
|
-
* // levels with lower priority. For example: 'error', 'warn' and 'info' will be logged when 'info' level is configured.
|
|
242
|
-
* //
|
|
243
|
-
* // Property `logger` represents the logging function which will be invoked for every log call with an acceptable level. The function should
|
|
244
|
-
* // take two string arguments `level` and `message`. The function should not execute any blocking or long-running operations
|
|
245
|
-
* // because it is often executed on a hot path.
|
|
246
|
-
* //
|
|
247
|
-
* // No logging is done by default. See `neo4j.logging` object that contains predefined logging implementations.
|
|
248
|
-
* logging: {
|
|
249
|
-
* level: 'info',
|
|
250
|
-
* logger: (level, message) => console.log(level + ' ' + message)
|
|
251
|
-
* },
|
|
252
|
-
*
|
|
253
|
-
* // Specify a custom server address resolver function used by the routing driver to resolve the initial address used to create the driver.
|
|
254
|
-
* // Such resolution happens:
|
|
255
|
-
* // * during the very first rediscovery when driver is created
|
|
256
|
-
* // * when all the known routers from the current routing table have failed and driver needs to fallback to the initial address
|
|
257
|
-
* //
|
|
258
|
-
* // In NodeJS environment driver defaults to performing a DNS resolution of the initial address using 'dns' module.
|
|
259
|
-
* // In browser environment driver uses the initial address as-is.
|
|
260
|
-
* // Value should be a function that takes a single string argument - the initial address. It should return an array of new addresses.
|
|
261
|
-
* // Address is a string of shape '<host>:<port>'. Provided function can return either a Promise resolved with an array of addresses
|
|
262
|
-
* // or array of addresses directly.
|
|
263
|
-
* resolver: function(address) {
|
|
264
|
-
* return ['127.0.0.1:8888', 'fallback.db.com:7687'];
|
|
265
|
-
* },
|
|
266
|
-
*
|
|
267
|
-
* // Configure filter for Notification objects returned in ResultSummary#notifications.
|
|
268
|
-
* // See SessionConfig#notificationFilter for usage instructions.
|
|
269
|
-
* notificationFilter: undefined,
|
|
270
|
-
*
|
|
271
|
-
* // Optionally override the default user agent name.
|
|
272
|
-
* userAgent: USER_AGENT
|
|
273
|
-
* }
|
|
274
|
-
*
|
|
275
150
|
* @param {string} url The URL for the Neo4j database, for instance "neo4j://localhost" and/or "bolt://localhost"
|
|
276
151
|
* @param {Map<string,string>} authToken Authentication credentials. See {@link auth} for helpers.
|
|
277
|
-
* @param {
|
|
152
|
+
* @param {Config} config Configuration object.
|
|
278
153
|
* @returns {Driver}
|
|
279
154
|
*/
|
|
280
155
|
function driver(url, authToken, config) {
|
|
281
156
|
if (config === void 0) { config = {}; }
|
|
282
157
|
assertString(url, 'Bolt URL');
|
|
283
158
|
var parsedUrl = urlUtil.parseDatabaseUrl(url);
|
|
284
|
-
// Determine
|
|
159
|
+
// Determine encryption/trust options from the URL.
|
|
285
160
|
var routing = false;
|
|
286
161
|
var encrypted = false;
|
|
287
162
|
var trust;
|
package/lib/version.js
CHANGED
|
@@ -26,4 +26,4 @@ Object.defineProperty(exports, "__esModule", { value: true });
|
|
|
26
26
|
// This is set up this way to keep the version in the code in
|
|
27
27
|
// sync with the npm package version, and to allow the build
|
|
28
28
|
// system to control version names at packaging time.
|
|
29
|
-
exports.default = '5.9.
|
|
29
|
+
exports.default = '5.9.2';
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "neo4j-driver",
|
|
3
|
-
"version": "5.9.
|
|
3
|
+
"version": "5.9.2",
|
|
4
4
|
"description": "The official Neo4j driver for Javascript",
|
|
5
5
|
"author": "Neo4j",
|
|
6
6
|
"license": "Apache-2.0",
|
|
@@ -80,9 +80,9 @@
|
|
|
80
80
|
"webpack": "^5.83.1"
|
|
81
81
|
},
|
|
82
82
|
"dependencies": {
|
|
83
|
-
"neo4j-driver-bolt-connection": "5.9.
|
|
84
|
-
"neo4j-driver-core": "5.9.
|
|
83
|
+
"neo4j-driver-bolt-connection": "5.9.2",
|
|
84
|
+
"neo4j-driver-core": "5.9.2",
|
|
85
85
|
"rxjs": "^7.8.0"
|
|
86
86
|
},
|
|
87
|
-
"gitHead": "
|
|
87
|
+
"gitHead": "c69a23fb3a8552cca8f0e685899d42ceb70e266c"
|
|
88
88
|
}
|