@sqlite.org/sqlite-wasm - npm Package Compare versions

Comparing version 3.44.1-build2 to 3.44.2-build1

package.json

 {
   "name": "@sqlite.org/sqlite-wasm",
-  "version": "3.44.1-build2",
+  "version": "3.44.2-build1",
   "description": "SQLite Wasm conveniently wrapped as an ES Module.",
@@ -42,3 +42,3 @@ "keywords": [
     "fix": "npx prettier . --write",
-
+    "prepare": "npm run build && npm run fix && npm run publint",
     "deploy": "npm run prepare && git add . && git commit -am 'New release' && git push && npm publish --access public"
@@ -45,0 +45,0 @@ },

sqlite-wasm/jswasm/sqlite3-opfs-async-proxy.js

@@ -67,7 +67,10 @@ /*
 
-  /** Will hold state copied to this object from the syncronous side of this API. */
+  /**
+   * Will hold state copied to this object from the syncronous side of
+   *      this API.
+   */
   const state = Object.create(null);
 
   /**
-   * Verbose:
+   * verbose:
    *
@@ -136,7 +139,7 @@ *      0 = no logging output
   /**
-   * __openFiles is a map of sqlite3_file pointers (integers) to metadata
-   * related to a given OPFS file handles. The pointers are, in this side of the
-   * interface, opaque file handle IDs provided by the synchronous part of this
-   * constellation. Each value is an object with a structure demonstrated in the
-   * xOpen() impl.
+   * __openFiles is a map of sqlite3_file pointers (integers) to
+   *      metadata related to a given OPFS file handles. The pointers are, in
+   *      this side of the interface, opaque file handle IDs provided by the
+   *      synchronous part of this constellation. Each value is an object
+   *      with a structure demonstrated in the xOpen() impl.
    */
@@ -146,7 +149,7 @@ const __openFiles = Object.create(null);
    * __implicitLocks is a Set of sqlite3_file pointers (integers) which were
-   * "auto-locked". i.e. those for which we obtained a sync access handle
-   * without an explicit xLock() call. Such locks will be released during db
-   * connection idle time, whereas a sync access handle obtained via xLock(), or
-   * subsequently xLock()'d after auto-acquisition, will not be released until
-   * xUnlock() is called.
+   *      "auto-locked".  i.e. those for which we obtained a sync access
+   *      handle without an explicit xLock() call. Such locks will be
+   *      released during db connection idle time, whereas a sync access
+   *      handle obtained via xLock(), or subsequently xLock()'d after
+   *      auto-acquisition, will not be released until xUnlock() is called.
    *
@@ -161,6 +164,6 @@ *      Maintenance reminder: if we relinquish auto-locks at the end of the
   /**
-   * Expects an OPFS file path. It gets resolved, such that ".." components are
-   * properly expanded, and returned. If the 2nd arg is true, the result is
-   * returned as an array of path elements, else an absolute path string is
-   * returned.
+   * Expects an OPFS file path. It gets resolved, such that ".."
+   *      components are properly expanded, and returned. If the 2nd arg is
+   *      true, the result is returned as an array of path elements, else an
+   *      absolute path string is returned.
    */
@@ -173,6 +176,6 @@ const getResolvedPath = function (filename, splitIt) {
   /**
-   * Takes the absolute path to a filesystem element. Returns an array of
-   * [handleOfContainingDir, filename]. If the 2nd argument is truthy then each
-   * directory element leading to the file is created along the way. Throws if
-   * any creation or resolution fails.
+   * Takes the absolute path to a filesystem element. Returns an array
+   *      of [handleOfContainingDir, filename]. If the 2nd argument is truthy
+   *      then each directory element leading to the file is created along
+   *      the way. Throws if any creation or resolution fails.
    */
@@ -192,10 +195,10 @@ const getDirForFilename = async function f(absFilename, createDirs = false) {
   /**
-   * If the given file-holding object has a sync handle attached to it, that
-   * handle is remove and asynchronously closed. Though it may sound sensible to
-   * continue work as soon as the close() returns (noting that it's
-   * asynchronous), doing so can cause operations performed soon afterwards,
-   * e.g. a call to getSyncHandle() to fail because they may happen out of order
-   * from the close(). OPFS does not guaranty that the actual order of
-   * operations is retained in such cases. i.e. always "await" on the result of
-   * this function.
+   * If the given file-holding object has a sync handle attached to it,
+   *      that handle is remove and asynchronously closed. Though it may
+   *      sound sensible to continue work as soon as the close() returns
+   *      (noting that it's asynchronous), doing so can cause operations
+   *      performed soon afterwards, e.g. a call to getSyncHandle() to fail
+   *      because they may happen out of order from the close(). OPFS does
+   *      not guaranty that the actual order of operations is retained in
+   *      such cases. i.e.  always "await" on the result of this function.
    */
@@ -245,5 +248,5 @@ const closeSyncHandle = async (fh) => {
   /**
-   * An experiment in improving concurrency by freeing up implicit locks sooner.
-   * This is known to impact performance dramatically but it has also shown to
-   * improve concurrency considerably.
+   * An experiment in improving concurrency by freeing up implicit locks
+   *      sooner. This is known to impact performance dramatically but it has
+   *      also shown to improve concurrency considerably.
    *
@@ -260,7 +263,7 @@ *      If fh.releaseImplicitLocks is truthy and fh is in __implicitLocks,
   /**
-   * An error class specifically for use with getSyncHandle(), the goal of which
-   * is to eventually be able to distinguish unambiguously between
-   * locking-related failures and other types, noting that we cannot currently
-   * do so because createSyncAccessHandle() does not define its exceptions in
-   * the required level of detail.
+   * An error class specifically for use with getSyncHandle(), the goal
+   *      of which is to eventually be able to distinguish unambiguously
+   *      between locking-related failures and other types, noting that we
+   *      cannot currently do so because createSyncAccessHandle() does not
+   *      define its exceptions in the required level of detail.
    *
@@ -305,5 +308,5 @@ *      2022-11-29: according to:
   /**
-   * Returns the sync access handle associated with the given file handle object
-   * (which must be a valid handle object, as created by xOpen()), lazily
-   * opening it if needed.
+   * Returns the sync access handle associated with the given file
+   *      handle object (which must be a valid handle object, as created by
+   *      xOpen()), lazily opening it if needed.
    *
@@ -377,3 +380,3 @@ *      In order to help alleviate cross-tab contention for a dabase, if
    * Stores the given value at state.sabOPView[state.opIds.rc] and then
-   * Atomics.notify()'s it.
+   *      Atomics.notify()'s it.
    */
@@ -392,7 +395,7 @@ const storeAndNotify = (opName, value) => {
   /**
-   * We track 2 different timers: the "metrics" timer records how much time we
-   * spend performing work. The "wait" timer records how much time we spend
-   * waiting on the underlying OPFS timer. See the calls to mTimeStart(),
-   * mTimeEnd(), wTimeStart(), and wTimeEnd() throughout this file to see how
-   * they're used.
+   * We track 2 different timers: the "metrics" timer records how much
+   *      time we spend performing work. The "wait" timer records how much
+   *      time we spend waiting on the underlying OPFS timer. See the calls
+   *      to mTimeStart(), mTimeEnd(), wTimeStart(), and wTimeEnd()
+   *      throughout this file to see how they're used.
    */
@@ -422,6 +425,6 @@ const __mTimer = Object.create(null);
   /**
-   * Gets set to true by the 'opfs-async-shutdown' command to quit the wait
-   * loop. This is only intended for debugging purposes: we cannot inspect this
-   * file's state while the tight waitLoop() is running and need a way to stop
-   * that loop for introspection purposes.
+   * Gets set to true by the 'opfs-async-shutdown' command to quit the
+   *      wait loop. This is only intended for debugging purposes: we cannot
+   *      inspect this file's state while the tight waitLoop() is running and
+   *      need a way to stop that loop for introspection purposes.
    */
@@ -431,5 +434,5 @@ let flagAsyncShutdown = false;
   /**
-   * Asynchronous wrappers for sqlite3_vfs and sqlite3_io_methods methods, as
-   * well as helpers like mkdir(). Maintenance reminder: members are in
-   * alphabetical order to simplify finding them.
+   * Asynchronous wrappers for sqlite3_vfs and sqlite3_io_methods
+   *      methods, as well as helpers like mkdir(). Maintenance reminder:
+   *      members are in alphabetical order to simplify finding them.
    */
@@ -773,4 +776,4 @@ const vfsAsyncImpls = {
     /**
-     * ACHTUNG: this code is 100% duplicated in the other half of this proxy!
-     * The documentation is maintained in the "synchronous half".
+     * ACHTUNG: this code is 100% duplicated in the other half of this
+     *        proxy! The documentation is maintained in the "synchronous half".
      */
@@ -777,0 +780,0 @@ if (state.s11n) return state.s11n;

sqlite-wasm/jswasm/sqlite3-worker1-promiser-bundler-friendly.js

@@ -146,6 +146,4 @@ /*
     );
-  }.bind({
-    currentScript: globalThis?.document?.currentScript,
-  }),
+  },
   onerror: (...args) => console.error('worker1 promiser error', ...args),
 };

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

3113530

increased by0.01%

Lines of code

60298

Number of medium supply chain risk alerts

27

decreased by-3.57%

No dependency changes