lopebase 0.2.0 → 0.3.1

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Jackalope Digital
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -30,10 +30,10 @@ In the folder of any project you run:
 npx lopebase
 ```
 
-1. **Scan.** It reads your `package.json` files, config file names, and the
-   variable *names* in example env files, then shows your stack, the services
-   you already use, and what is missing (for example analytics or error
-   tracking).
+1. **Scan.** After you say yes, it reads your dependency names, config file
+   names, and the variable *names* in example env files, then shows your
+   stack, the services you already use, and what it did not find (for example
+   analytics or error logging). You see each thing it reads as it reads it.
 2. **Connect this computer.** It opens your LopeBase workspace and shows a
    short code. Check it matches and press Connect.
 3. **Pick what to connect.** Services already in your code are ticked; the
@@ -45,6 +45,32 @@ npx lopebase
 
 No agent installed? It prints the prompt for you to paste instead.
 
+It animates a little in an interactive terminal. `--no-motion` or
+`LOPEBASE_NO_MOTION=1` turns that off; CI and pipes never animate.
+
+## What it recognizes
+
+Made for web products, and fine with anything else:
+
+- **Frameworks:** Next.js, Astro, SvelteKit, Remix, React Router, Nuxt,
+  Gatsby, Docusaurus, Eleventy, Hugo, Jekyll, Angular, SolidStart, Qwik,
+  TanStack Start, Vue, React and Vite apps, plain static sites, Django, Flask,
+  FastAPI, Rails, Laravel, WordPress, Express, Fastify, NestJS, Hono, Expo, and
+  Electron.
+- **Languages:** JavaScript and TypeScript, Python, Ruby, PHP, Go, and Rust,
+  from their own manifests.
+- **Hosting, data, email, billing, and sign-in:** Cloudflare, Vercel, Netlify,
+  Fly.io, Render, Railway, Firebase, Amplify, Heroku, GitHub Pages, and Docker;
+  Supabase, Convex, Neon, Postgres, MySQL, MongoDB, D1, Prisma, Drizzle, and
+  more; Resend, Sequenzy, SendGrid, Postmark; Stripe, Polar, Lemon Squeezy,
+  Paddle; Clerk, WorkOS, Better Auth, Auth.js, and others.
+- **Ready to connect to LopeBase:** PostHog, Google Analytics, Sentry, Stripe,
+  Polar, Supabase, Resend, Sequenzy, and GitHub when your code uses them; plus
+  Search Console, Bing, and an uptime check for any website.
+- **Your site's address**, from `homepage`, wrangler routes, `CNAME`, a
+  framework config (`site`, `siteUrl`, `baseURL`), or the canonical tag in
+  `index.html`. **Your GitHub repo**, from the git remote.
+
 ## Commands
 
 | Command | What it does |
@@ -59,9 +85,12 @@ No agent installed? It prints the prompt for you to paste instead.
 
 ## What it reads, and what it keeps
 
-- **Reads:** `package.json` files at the root and in `apps/`, `packages/`,
-  and similar folders; config file names such as `wrangler.toml` or
-  `vercel.json`; and the variable names in `.env.example` style files.
+- **Reads:** `package.json` files (and `requirements.txt`, `pyproject.toml`,
+  `Gemfile`, `composer.json`, `go.mod`, `Cargo.toml`) at the root, in your
+  workspace folders, and in `apps/`, `packages/`, and similar folders; config
+  file names such as `wrangler.toml` or `vercel.json`; the site address in a
+  few config files; your git remote's address; and the variable names in
+  `.env.example` style files.
 - **Never reads** a real `.env` file, and never sends a value anywhere. Only
   names leave your machine, and only to your own workspace.
 - **Keeps** one thing: an agent token in `~/.config/lopebase/auth.json`,