You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(lynxtron-go): unblock packaged-app showcase install & rename deep link scheme (#19)
* fix(lynxtron-go): include @lynx-js/lynxtron in packaged app.asar
lynxtron-builder's app-builder-lib patch uses the outer
lynxtron-go/package.json#dependencies as the allowlist when collecting
node_modules into app.asar. Having @lynx-js/lynxtron in devDependencies
caused it to be filtered out, so preload.js failed at runtime with
"Cannot find module '@lynx-js/lynxtron'" after install.
* feat(lynxtron-go): rename deep link scheme to lynxtron-go://
Aligns the URL scheme with the app name so it doesn't collide with the
underlying @lynx-js/lynxtron runtime namespace. Updates the shared
scheme constant, macOS CFBundleURLSchemes, in-app help page, and tests.
* chore(config): bump to 0.0.2 to republish with expanded catalog deps
The previously published @lynxtron-examples/config@0.0.1 tarball still
carried `catalog:` refs in its `dependencies` (pnpm publish did not
expand them). That caused ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER
when the Lynxtron GO app ran `pnpm install` inside the workspace after
fetching a showcase. Republishing from a pnpm workspace produces a
clean tarball with real version specifiers.
* feat(lynxtron-go): add lynxtron-go://open?url= short deep link alias
Accept `open` as an alternate host to `lynxview_page` for the bundle
URL intent, and let both hosts read either `url=` or `bundle=`. Same
http(s)-only guard, same bundle-url-open intent, so downstream dispatch
does not change. Updates help page and tests.
Also folds in the changeset for the earlier packaged-app fixes (asar
runtime dep + deep link scheme rename to lynxtron-go://).
* chore(deps): sync pnpm-lock.yaml after moving @lynx-js/lynxtron to dependencies
CI failed with ERR_PNPM_OUTDATED_LOCKFILE because the earlier commit
that moved @lynx-js/lynxtron from devDependencies to dependencies did
not regenerate the lockfile. Only pnpm-lock.yaml changes here: the
@lynx-js/lynxtron entry moves between the two importer sections; no
version bump.
Republish so `package.json``dependencies` carry real version specifiers instead of the `catalog:` protocol. The previously published `0.0.1` tarball still contained `catalog:` refs, which caused `pnpm install` to fail with `ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER` when the Lynxtron GO app tried to install a fetched showcase.
- Move `@lynx-js/lynxtron` from `devDependencies` to `dependencies` so `electron-builder` (via the `lynxtron-builder` patch that uses the app's own `package.json#dependencies` as the app.asar allowlist) actually includes it in the packaged app. Fixes `Cannot find module '@lynx-js/lynxtron'` at showcase-run time.
6
+
- Rename the deep link URL scheme from `lynxtron://` to `lynxtron-go://` to avoid overlapping with the underlying `@lynx-js/lynxtron` runtime namespace. Covers the shared scheme constant, macOS `CFBundleURLSchemes`, in-app help page, and tests.
7
+
- Add `lynxtron-go://open?url=<bundle-url>` as a short alias for `lynxtron-go://lynxview_page?bundle=<bundle-url>` so external tools can hand out a shorter deep link when previewing a hosted `.lynx.bundle`. Both hosts accept `url=` and `bundle=` interchangeably and enforce the same http(s)-only guard.
0 commit comments