Conversation
Adds @tomic/ng-bridge-react (from the sibling atomic-ng-bridge repo) and mounts its badge next to the router, plus its panel on the Sync page. That component mirrors the current local-only drive into a NextGraph document, live, with no AtomicServer in the loop. Deliberately the whole footprint in this repo: every piece of NextGraph code lives in the imported package. It renders nothing, and loads nothing, unless enabled with `?ngbridge=1`. Dropping the mirror is reverting this commit. Vite needs three things for it, each found by running it rather than reading: - `worker.plugins` applies `vite-plugin-wasm` to worker builds. It does not inherit from the main plugin array, and without it the worker fails to build and the mirror silently falls back to running its wasm on the main thread, where a long query competes with rendering. - `server.fs.allow` includes the mirror's checkout when it is linked from a sibling directory. Vite serves the worker entry over `/@fs/` as its own request and refuses paths outside the workspace root, so the worker 403s. Installed from a registry it lives in node_modules and none of this applies. - `@ng-org/lib-wasm` joins `optimizeDeps.exclude`, for the reason this file already documents for loro-crdt: a wasm dep that esbuild prebundles has its init hang forever rather than fail. All three are inert when the mirror is not enabled.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds @tomic/ng-bridge-react (from the sibling atomic-ng-bridge repo) and mounts its badge next to the router, plus its panel on the Sync page. That component mirrors the current local-only drive into a NextGraph document, live, with no AtomicServer in the loop.
Deliberately the whole footprint in this repo: every piece of NextGraph code lives in the imported package. It renders nothing, and loads nothing, unless enabled with
?ngbridge=1. Dropping the mirror is reverting this commit.Vite needs three things for it, each found by running it rather than reading:
worker.pluginsappliesvite-plugin-wasmto worker builds. It does not inherit from the main plugin array, and without it the worker fails to build and the mirror silently falls back to running its wasm on the main thread, where a long query competes with rendering.server.fs.allowincludes the mirror's checkout when it is linked from a sibling directory. Vite serves the worker entry over/@fs/as its own request and refuses paths outside the workspace root, so the worker 403s. Installed from a registry it lives in node_modules and none of this applies.@ng-org/lib-wasmjoinsoptimizeDeps.exclude, for the reason this file already documents for loro-crdt: a wasm dep that esbuild prebundles has its init hang forever rather than fail.All three are inert when the mirror is not enabled.
Related Issues
closes #number
Checklist