ilml-plugin-linkedin 1.11.1 → 1.11.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/CHANGELOG.md +4 -0
- package/dist/enrichProfiles.mjs +49 -254
- package/dist/messageBot.mjs +99 -304
- package/dist/scout.mjs +49 -254
- package/dist/syncAll.mjs +92 -297
- package/dist/verifyAbout.mjs +9 -214
- package/dist/viewers.mjs +53 -258
- package/dist/visit.mjs +50 -255
- package/ilml-plugin.json +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.11.2
|
|
4
|
+
- **Plugin loads again when installed via `ilml plugin install linkedin`.** v1.11.0 introduced a transitive dependency (`debug` via Puppeteer's stealth plugin) that uses `require('tty')` at runtime — esbuild can't bundle dynamic CommonJS requires into an ESM module, so any `ilml linkedin <command>` died on startup with `Dynamic require of "tty" is not supported`. The build now uses `packages: 'external'` to keep all `node_modules` deps unbundled at runtime (installed by npm into the plugin directory as usual). Same install footprint, no schema change — just the bundle behaves correctly.
|
|
5
|
+
- No schema migration; existing data files unchanged.
|
|
6
|
+
|
|
3
7
|
## 1.11.1
|
|
4
8
|
- **`sync-all` now backfills profile URLs for card-only stub conversations.** When the inbox scan saw a conversation card but never successfully opened its thread (e.g. an earlier sync failed mid-read, or the thread was created from outbound activity alone), the entry was stuck with 0 stored messages and no `profileUrl` — and the previous "re-read to capture URL" check required `messages.length > 0`, so these stubs were never picked up again. The condition now triggers re-read on any sign of activity (stored messages OR sidebar preview), so empty-but-recently-active stubs are queued for thread-open on the next sync. Net effect on long-running databases: dozens of conversations that had only sidebar metadata get their profile URL and message body filled in over the next few sync passes. Backwards-compatible — only adds re-read attempts that previously weren't made.
|
|
5
9
|
- No schema migration; existing data files unchanged.
|