vite-plugin-specter 0.6.1 → 0.7.1
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/README.md +13 -0
- package/dist/client.js +457 -55
- package/dist/extension-chrome/content.js +457 -55
- package/dist/extension-chrome/manifest.json +1 -1
- package/dist/extension-firefox/content.js +457 -55
- package/dist/extension-firefox/manifest.json +1 -1
- package/dist/index.cjs +457 -55
- package/dist/index.js +457 -55
- package/extension/content.js +457 -55
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -112,6 +112,19 @@ font: Inter 400 19/28.5 · color: #c7cbd1
|
|
|
112
112
|
|
|
113
113
|
Paste into Claude, Cursor, or any AI assistant — the instructions travel with the elements, so there's nothing left to explain.
|
|
114
114
|
|
|
115
|
+
## Share comments with another person
|
|
116
|
+
|
|
117
|
+
Specs aren't only for your AI — you can send them to a **person**. Mark comments on a page, open the Specs panel (**L**), and click **Share**. Specter copies a link; whoever opens it — on the same page, with Specter installed — sees your comments re-anchored on the exact same elements.
|
|
118
|
+
|
|
119
|
+
- **Comments only.** Only your notes and how to re-find each element travel — never the CSS properties or measurements. You're sharing feedback, not internals.
|
|
120
|
+
- **Same page, same element.** Comments re-anchor by a source locator, not screen coordinates. If the page changed so an element is gone or different, that comment shows as **MISSING** in the panel (with the reason) instead of landing on the wrong spot.
|
|
121
|
+
- **A link, or a file.** Small reviews copy as a normal link (`…/pricing#spx=…`) you paste into Slack or a message — the link is both the destination and the payload, so it opens the right page automatically. A large batch (or a page that uses `#`-routing) downloads a `comments.specter.json` file to send instead; use the **Import** button to open one you receive.
|
|
122
|
+
- **Zero backend.** The comments travel inside the link or file itself — no accounts, no server. One-way (no threads).
|
|
123
|
+
|
|
124
|
+
**Both people need Specter (v0.7+).** This is where the **browser extension** shines: it works on any deployed or staging URL, so two people looking at the same prototype can trade feedback without a shared dev server. A share link opened without Specter just shows the normal page — nothing breaks.
|
|
125
|
+
|
|
126
|
+
> Specter also ships as a **browser extension** for Chrome and Firefox, which runs on *any* website (no Vite required). The Share Comments flow above is designed for it. See the [GitHub repo](https://github.com/setugk/vite-plugin-specter) for links.
|
|
127
|
+
|
|
115
128
|
## Shortcut reference
|
|
116
129
|
|
|
117
130
|
| Action | Shortcut |
|