querysub 0.433.0 → 0.436.0

package/src/storage/fileSystemPointer.ts

@@ -1,72 +1,72 @@
-import { lazy } from "socket-function/src/caching";
-import { nextId } from "socket-function/src/misc";
-
-const objectStoreName = "fileSystemPointerDB";
-const db = lazy(async () => {
-    let db = indexedDB.open("fileSystemPointerDB_f298e962-bd8a-46b9-8098-25db633f4ed3", 1);
-    db.addEventListener("upgradeneeded", () => {
-        db.result.createObjectStore(objectStoreName, {});
-    });
-    await new Promise(resolve => db.addEventListener("success", resolve));
-    return db.result;
-});
-async function getTransaction() {
-    let database = await db();
-    if (!database) return undefined;
-    return database.transaction(objectStoreName, "readwrite").objectStore(objectStoreName);
-}
-async function write(key: string, value: FileSystemFileHandle | FileSystemDirectoryHandle) {
-    let transaction = await getTransaction();
-    if (!transaction) return;
-    let req = transaction.put(value, key);
-    await new Promise((resolve, reject) => {
-        req.addEventListener("success", resolve);
-        req.addEventListener("error", reject);
-    });
-}
-async function read(key: string): Promise<FileSystemFileHandle | FileSystemDirectoryHandle | undefined> {
-    let transaction = await getTransaction();
-    if (!transaction) return;
-    let req = transaction.get(key);
-    await new Promise((resolve, reject) => {
-        req.addEventListener("success", resolve);
-        req.addEventListener("error", reject);
-    });
-    return req.result;
-}
-
-export type FileSystemPointer = string;
-export async function storeFileSystemPointer(config: {
-    mode: "read" | "readwrite";
-    handle: FileSystemFileHandle | FileSystemDirectoryHandle;
-}): Promise<FileSystemPointer> {
-    await (config.handle as any).requestPermission({ mode: config.mode });
-    let key = nextId() + "_" + config.mode;
-    await write(key, config.handle);
-    return key;
-}
-
-export async function getFileSystemPointer(config: {
-    pointer: FileSystemPointer;
-}): Promise<{
-    // NOTE: We have to call requestPermission, so... user activation is required (as in,
-    //  this need to be called inside of a button).
-    // IMPORTANT! In some circumstances user activation is not required (with multiple tabs,
-    //      and potentially with https://developer.chrome.com/blog/persistent-permissions-for-the-file-system-access-api),
-    //      so... trying to call onUserActivation immmediately is a good idea (although it might throw).
-    onUserActivation(modeOverride?: "read" | "readwrite"): Promise<FileSystemFileHandle | FileSystemDirectoryHandle>
-} | undefined
-> {
-    const handle = await read(config.pointer);
-    if (!handle) return;
-    let mode = config.pointer.split("_").at(-1);
-    return {
-        async onUserActivation(modeOverride) {
-            let testMode = await (handle as any).queryPermission({ mode: mode });
-            if (testMode !== mode) {
-                await (handle as any).requestPermission({ mode: modeOverride ?? mode });
-            }
-            return handle;
-        }
-    };
+import { lazy } from "socket-function/src/caching";
+import { nextId } from "socket-function/src/misc";
+
+const objectStoreName = "fileSystemPointerDB";
+const db = lazy(async () => {
+    let db = indexedDB.open("fileSystemPointerDB_f298e962-bd8a-46b9-8098-25db633f4ed3", 1);
+    db.addEventListener("upgradeneeded", () => {
+        db.result.createObjectStore(objectStoreName, {});
+    });
+    await new Promise(resolve => db.addEventListener("success", resolve));
+    return db.result;
+});
+async function getTransaction() {
+    let database = await db();
+    if (!database) return undefined;
+    return database.transaction(objectStoreName, "readwrite").objectStore(objectStoreName);
+}
+async function write(key: string, value: FileSystemFileHandle | FileSystemDirectoryHandle) {
+    let transaction = await getTransaction();
+    if (!transaction) return;
+    let req = transaction.put(value, key);
+    await new Promise((resolve, reject) => {
+        req.addEventListener("success", resolve);
+        req.addEventListener("error", reject);
+    });
+}
+async function read(key: string): Promise<FileSystemFileHandle | FileSystemDirectoryHandle | undefined> {
+    let transaction = await getTransaction();
+    if (!transaction) return;
+    let req = transaction.get(key);
+    await new Promise((resolve, reject) => {
+        req.addEventListener("success", resolve);
+        req.addEventListener("error", reject);
+    });
+    return req.result;
+}
+
+export type FileSystemPointer = string;
+export async function storeFileSystemPointer(config: {
+    mode: "read" | "readwrite";
+    handle: FileSystemFileHandle | FileSystemDirectoryHandle;
+}): Promise<FileSystemPointer> {
+    await (config.handle as any).requestPermission({ mode: config.mode });
+    let key = nextId() + "_" + config.mode;
+    await write(key, config.handle);
+    return key;
+}
+
+export async function getFileSystemPointer(config: {
+    pointer: FileSystemPointer;
+}): Promise<{
+    // NOTE: We have to call requestPermission, so... user activation is required (as in,
+    //  this need to be called inside of a button).
+    // IMPORTANT! In some circumstances user activation is not required (with multiple tabs,
+    //      and potentially with https://developer.chrome.com/blog/persistent-permissions-for-the-file-system-access-api),
+    //      so... trying to call onUserActivation immmediately is a good idea (although it might throw).
+    onUserActivation(modeOverride?: "read" | "readwrite"): Promise<FileSystemFileHandle | FileSystemDirectoryHandle>
+} | undefined
+> {
+    const handle = await read(config.pointer);
+    if (!handle) return;
+    let mode = config.pointer.split("_").at(-1);
+    return {
+        async onUserActivation(modeOverride) {
+            let testMode = await (handle as any).queryPermission({ mode: mode });
+            if (testMode !== mode) {
+                await (handle as any).requestPermission({ mode: modeOverride ?? mode });
+            }
+            return handle;
+        }
+    };
 }

package/src/test/heapProcess.ts

@@ -1,36 +1,36 @@
-import { formatNumber } from "socket-function/src/formatting/format";
-import { parseHeapSnapshot, processAndSummarizeHeapsnapshot } from "../heapDumps";
-import fs from "fs";
-
-async function heapProcess() {
-    /*
-    let targetRatePerSecond = 50;
-    let startTime = Date.now();
-    
-    for(let i = 0; i < 300 * 300; i++) {
-        sat_functions.setValues([i]);
-        
-        while (true) {
-            let rate = i / (Date.now() - startTime) * 1000;
-            if(rate < targetRatePerSecond) break;
-            await delay(16);
-        }
-    }
-    */
-
-    let buffer = fs.readFileSync("./heapdump.heapsnapshot");
-    let parsed = await parseHeapSnapshot("stressTest", buffer, () => { });
-
-    let snapshot = await processAndSummarizeHeapsnapshot(parsed, () => { }, {
-
-    });
-    console.log();
-
-    console.log(`Total ${formatNumber(snapshot.total)}`);
-    let values = Object.values(snapshot.summary);
-    values.sort((a, b) => b.sum - a.sum);
-    for (let value of values.slice(0, 100)) {
-        console.log(`${formatNumber(value.sum)} (${value.count})`.padEnd(20, "") + " " + value.key + ` (ex id ${value.firstId})`);
-    }
-}
+import { formatNumber } from "socket-function/src/formatting/format";
+import { parseHeapSnapshot, processAndSummarizeHeapsnapshot } from "../heapDumps";
+import fs from "fs";
+
+async function heapProcess() {
+    /*
+    let targetRatePerSecond = 50;
+    let startTime = Date.now();
+    
+    for(let i = 0; i < 300 * 300; i++) {
+        sat_functions.setValues([i]);
+        
+        while (true) {
+            let rate = i / (Date.now() - startTime) * 1000;
+            if(rate < targetRatePerSecond) break;
+            await delay(16);
+        }
+    }
+    */
+
+    let buffer = fs.readFileSync("./heapdump.heapsnapshot");
+    let parsed = await parseHeapSnapshot("stressTest", buffer, () => { });
+
+    let snapshot = await processAndSummarizeHeapsnapshot(parsed, () => { }, {
+
+    });
+    console.log();
+
+    console.log(`Total ${formatNumber(snapshot.total)}`);
+    let values = Object.values(snapshot.summary);
+    values.sort((a, b) => b.sum - a.sum);
+    for (let value of values.slice(0, 100)) {
+        console.log(`${formatNumber(value.sum)} (${value.count})`.padEnd(20, "") + " " + value.key + ` (ex id ${value.firstId})`);
+    }
+}
 heapProcess().catch(e => console.error(e)).finally(() => process.exit());

package/src/zip.ts

@@ -1,15 +1,15 @@
-import { isNode } from "socket-function/src/misc";
-import { measureBlock, measureFnc } from "socket-function/src/profiling/measure";
-import zlib from "zlib";
-import * as pako from "pako";
-
-import { setFlag } from "socket-function/require/compileFlags";
-import { unzipThreaded } from "./zipThreaded";
-import debugbreak from "debugbreak";
-import { formatNumber } from "socket-function/src/formatting/format";
-import { runInSerial } from "socket-function/src/batching";
-import { MaybePromise } from "socket-function/src/types";
-import { Zip } from "socket-function/src/Zip";
-setFlag(require, "pako", "allowclient", true);
-
-export { Zip };
+import { isNode } from "socket-function/src/misc";
+import { measureBlock, measureFnc } from "socket-function/src/profiling/measure";
+import zlib from "zlib";
+import * as pako from "pako";
+
+import { setFlag } from "socket-function/require/compileFlags";
+import { unzipThreaded } from "./zipThreaded";
+import debugbreak from "debugbreak";
+import { formatNumber } from "socket-function/src/formatting/format";
+import { runInSerial } from "socket-function/src/batching";
+import { MaybePromise } from "socket-function/src/types";
+import { Zip } from "socket-function/src/Zip";
+setFlag(require, "pako", "allowclient", true);
+
+export { Zip };

package/tsconfig.json

@@ -1,27 +1,27 @@
-{
-    "compilerOptions": {
-        "strict": true,
-        "module": "CommonJS",
-        "esModuleInterop": true,
-        "allowSyntheticDefaultImports": true,
-        "moduleResolution": "node",
-        "target": "es2018",
-        "lib": [
-            "ESNext",
-            "dom",
-            "dom.iterable"
-        ],
-        "jsx": "react",
-        "alwaysStrict": true,
-        "jsxFactory": "qreact.createElement",
-        "jsxFragmentFactory": "qreact.Fragment",
-        "types": [
-            "node",
-        ],
-        "experimentalDecorators": true,
-        "emitDecoratorMetadata": false,
-        "skipLibCheck": true,
-        "inlineSourceMap": true,
-        "inlineSources": true,
-    }
+{
+    "compilerOptions": {
+        "strict": true,
+        "module": "CommonJS",
+        "esModuleInterop": true,
+        "allowSyntheticDefaultImports": true,
+        "moduleResolution": "node",
+        "target": "es2018",
+        "lib": [
+            "ESNext",
+            "dom",
+            "dom.iterable"
+        ],
+        "jsx": "react",
+        "alwaysStrict": true,
+        "jsxFactory": "qreact.createElement",
+        "jsxFragmentFactory": "qreact.Fragment",
+        "types": [
+            "node",
+        ],
+        "experimentalDecorators": true,
+        "emitDecoratorMetadata": false,
+        "skipLibCheck": true,
+        "inlineSourceMap": true,
+        "inlineSources": true,
+    }
 }

package/yarnSpec.txt

@@ -1,56 +1,56 @@
-- better yarn, `packagedownload`?
-
-ACTUALLY, a lot of this, BUT, have the config format just entirely describe the on disk format, being relative to where each package is located. That way it is obvious how you will change how a specific package resolves just inside of another package, or if one package is using a custom version, etc, etc.
-
-`npm -run packagedownload add package-name`, `npm -run packagedownload install`
-    add
-        --dry-run
-        --force
-        --update
-        --dev
-        --nolink
-    install
-        --dry-run
-        --force
-        --update
-        --nolink
-- DON'T run scripts by default, only running them if requested via `"execute": {}` in the package.json configuration
-    - With a "request-execute" field, which warns if you use a package and don't let it execute (it will still run it though)
-- On install performs a "light" check, only checking the "package.json".version of packages (or package, if a package is specified), not updating anything that looks up to date
-    - Has a --force flag, which will always delete all packages and install a new one (or rather, install all packages, as we will always delete and install the new one when we are installing)
-- Still supports a --production mode, which doesn't install dev dependencies
-- HAS to support "cpu", and "os" restrictions
-    - But, still support "ignore-engines", to skip these
-- ALWAYS flat, warning on conflicts, using package "resolutions" to decide which one to use
-    - Although, maybe we can have "sandbox", which allows certain dependencies to be told to install all of their dependencies as nested? We won't be able to do partial sandboxing, unless the package is a few levels deep, and we pick the package directly above it (which doesn't give us full control, but is probably enough).
-- Call the lock file `resolvedversions.json`, as it isn't for locking, it is for specifying which versions of packages should be used (if compatible with the rough version in package.json)
-- Avoid nesting automatically, by having any install check if the current folder is in a node_modules folder, and if so uses the lock file above that, and installs the dependencies as siblings in that node_modules folder
-    - Allow packages to use `{ "force-sandbox": true }`, to force their dependencies to be installed in a nested node_modules (sandboxing which also cause the child yarn.lock to be checked before the parent yarn.lock)
-- Greatly simplified lock file, given that we generally won't have nested dependencies
-    - The lock file can give more metadata, such as the full chain of dependencies to the root package.json dependency, as well as package sizes and file counts
-    - Marks which dependencies are dev only (or only included because of a dev only dependency)
-- Support for "link" inside of the package json, which instead works like: `{ "local": { "shard": "../shard/" } }`, which uses those paths when they exist
-    - A "nolink" option will disable this
-    - Creates symlinks
-        - Makes symlinks for all nested dependencies as well
-        - Adds metadata in the lock file to indicate the modules are being symlinked?
-- Ability to install only a specific package, aka, `install shard`, which uses the version in the lock file (or package.json)
-    - typenode can start installing on require, only installing the required package
-        - There would have to be a way to turn it off, ex, with `typenodecompat`, which wouldn't install packages. That way you could use typenode without messing up your node_modules folders
-            - This mode could also store the dist folders somewhere else, or even... just not store them, eliminating caching?
-        - We could even use packagedownload via an import, so we don't need to spawn a new processes!
-            - This would allow packagedownload to maintain various caches, making it a lot more efficient when called multiple times.
-        - Add a TODO to support some form of tree-shaking. As in, if we detect out of the module only "x" and "y" are included, then we can strip the file of everything unrelated to "x" and "y" (which is not easy, but... not REALLY hard either). The idea, is not to reduce file size (who cares about that?), but actually to create unused requires, which we can then strip as well!
-            - We would need a flag to know if required modules have side-effects or not (package.json has a flag for this, and we can also support a `module.sideeffects = true` flag)
-            - And, we might as well have a package.json flag to set side-effects on nested packages, probably recursively.
-    - If the package is marked with "execute" it will be recursively installed as well, unless it has "no-recursive" in the package.json
-- Can be added to a package directly, which ADDS A BOOTSTRAPPER, by default, as a .js file, and adds a reference to a new scripts step ("packagedownload.js"?), or some similar step, in package.json. It can then be also called in your runs steps, ex, `node ./packagedownload.js && npm -run typenode ./index.ts`, which then allows `npm -run start` to work after an install (heck, you could even do `git clone git@github.com/user/repo.git ~/repo && cd ~/repo && git -run start`, to easily install it on any system that just has node and git)
-    - Eventually we could add the ability to install node, using the node version from the package.json (using the upper limit, ex `>=11 <15`, would use node 15), which would mean basically any system could use it.
-- Maybe use a global package download cache (which is maintained and kept below a certain percent of available space!)
-- `--update-check` and `--update`, to deal with updating yarn.lock (-check just checks and logs potential updates)
-- ALSO, "sources", which can be used to map packages to servers other than npm! Ex, github, etc. BUT, unlike the other way of doing it, versions are still supported!
-    - `{ "sources": { "source-map-support": "https://github.com/user/source-map-support" } }`
-        - Also supports npm, so you can switch out a package (for your dependencies too), easily
-    - ALSO, could add support for "dependencies2", to prevent npm and yarn from installing the dependencies (as they don't support "sources"), allowing the package to install them at runtime, allowing for better compatibility
-    - In conjunction with optionalDependencies make it possible to add dependencies that don't exist in npm
-    - The lock file will have to mark who set the source, potentially giving multiple setters, with the highest being the one that actual sets the source.
+- better yarn, `packagedownload`?
+
+ACTUALLY, a lot of this, BUT, have the config format just entirely describe the on disk format, being relative to where each package is located. That way it is obvious how you will change how a specific package resolves just inside of another package, or if one package is using a custom version, etc, etc.
+
+`npm -run packagedownload add package-name`, `npm -run packagedownload install`
+    add
+        --dry-run
+        --force
+        --update
+        --dev
+        --nolink
+    install
+        --dry-run
+        --force
+        --update
+        --nolink
+- DON'T run scripts by default, only running them if requested via `"execute": {}` in the package.json configuration
+    - With a "request-execute" field, which warns if you use a package and don't let it execute (it will still run it though)
+- On install performs a "light" check, only checking the "package.json".version of packages (or package, if a package is specified), not updating anything that looks up to date
+    - Has a --force flag, which will always delete all packages and install a new one (or rather, install all packages, as we will always delete and install the new one when we are installing)
+- Still supports a --production mode, which doesn't install dev dependencies
+- HAS to support "cpu", and "os" restrictions
+    - But, still support "ignore-engines", to skip these
+- ALWAYS flat, warning on conflicts, using package "resolutions" to decide which one to use
+    - Although, maybe we can have "sandbox", which allows certain dependencies to be told to install all of their dependencies as nested? We won't be able to do partial sandboxing, unless the package is a few levels deep, and we pick the package directly above it (which doesn't give us full control, but is probably enough).
+- Call the lock file `resolvedversions.json`, as it isn't for locking, it is for specifying which versions of packages should be used (if compatible with the rough version in package.json)
+- Avoid nesting automatically, by having any install check if the current folder is in a node_modules folder, and if so uses the lock file above that, and installs the dependencies as siblings in that node_modules folder
+    - Allow packages to use `{ "force-sandbox": true }`, to force their dependencies to be installed in a nested node_modules (sandboxing which also cause the child yarn.lock to be checked before the parent yarn.lock)
+- Greatly simplified lock file, given that we generally won't have nested dependencies
+    - The lock file can give more metadata, such as the full chain of dependencies to the root package.json dependency, as well as package sizes and file counts
+    - Marks which dependencies are dev only (or only included because of a dev only dependency)
+- Support for "link" inside of the package json, which instead works like: `{ "local": { "shard": "../shard/" } }`, which uses those paths when they exist
+    - A "nolink" option will disable this
+    - Creates symlinks
+        - Makes symlinks for all nested dependencies as well
+        - Adds metadata in the lock file to indicate the modules are being symlinked?
+- Ability to install only a specific package, aka, `install shard`, which uses the version in the lock file (or package.json)
+    - typenode can start installing on require, only installing the required package
+        - There would have to be a way to turn it off, ex, with `typenodecompat`, which wouldn't install packages. That way you could use typenode without messing up your node_modules folders
+            - This mode could also store the dist folders somewhere else, or even... just not store them, eliminating caching?
+        - We could even use packagedownload via an import, so we don't need to spawn a new processes!
+            - This would allow packagedownload to maintain various caches, making it a lot more efficient when called multiple times.
+        - Add a TODO to support some form of tree-shaking. As in, if we detect out of the module only "x" and "y" are included, then we can strip the file of everything unrelated to "x" and "y" (which is not easy, but... not REALLY hard either). The idea, is not to reduce file size (who cares about that?), but actually to create unused requires, which we can then strip as well!
+            - We would need a flag to know if required modules have side-effects or not (package.json has a flag for this, and we can also support a `module.sideeffects = true` flag)
+            - And, we might as well have a package.json flag to set side-effects on nested packages, probably recursively.
+    - If the package is marked with "execute" it will be recursively installed as well, unless it has "no-recursive" in the package.json
+- Can be added to a package directly, which ADDS A BOOTSTRAPPER, by default, as a .js file, and adds a reference to a new scripts step ("packagedownload.js"?), or some similar step, in package.json. It can then be also called in your runs steps, ex, `node ./packagedownload.js && npm -run typenode ./index.ts`, which then allows `npm -run start` to work after an install (heck, you could even do `git clone git@github.com/user/repo.git ~/repo && cd ~/repo && git -run start`, to easily install it on any system that just has node and git)
+    - Eventually we could add the ability to install node, using the node version from the package.json (using the upper limit, ex `>=11 <15`, would use node 15), which would mean basically any system could use it.
+- Maybe use a global package download cache (which is maintained and kept below a certain percent of available space!)
+- `--update-check` and `--update`, to deal with updating yarn.lock (-check just checks and logs potential updates)
+- ALSO, "sources", which can be used to map packages to servers other than npm! Ex, github, etc. BUT, unlike the other way of doing it, versions are still supported!
+    - `{ "sources": { "source-map-support": "https://github.com/user/source-map-support" } }`
+        - Also supports npm, so you can switch out a package (for your dependencies too), easily
+    - ALSO, could add support for "dependencies2", to prevent npm and yarn from installing the dependencies (as they don't support "sources"), allowing the package to install them at runtime, allowing for better compatibility
+    - In conjunction with optionalDependencies make it possible to add dependencies that don't exist in npm
+    - The lock file will have to mark who set the source, potentially giving multiple setters, with the highest being the one that actual sets the source.