@uge/payo 1.3.0 → 1.4.0
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 +4 -4
- package/dist/index.js +164 -163
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -144,8 +144,8 @@ guidance files straight into your repo.
|
|
|
144
144
|
|
|
145
145
|
Payo isn't just for empty repos. Run it in an established project and it **reads
|
|
146
146
|
what's already there** — `package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`,
|
|
147
|
-
`composer.json`, lockfiles, tool configs, and the folder layout — to figure out
|
|
148
|
-
your stack across **TypeScript/JavaScript, Python, Go, Rust, and
|
|
147
|
+
`composer.json`, `*.csproj`, `pom.xml`, `build.gradle`, `Gemfile`, lockfiles, tool configs, and the folder layout — to figure out
|
|
148
|
+
your stack across **TypeScript/JavaScript, Python, Go, Rust, PHP, C#, Java, and Ruby**, then pre-fills the questionnaire
|
|
149
149
|
from that evidence. You confirm or tweak instead of typing it all out.
|
|
150
150
|
|
|
151
151
|
When detection finds a manifest, you get two quick choices:
|
|
@@ -191,8 +191,8 @@ Each tool gets files in its own native format and location:
|
|
|
191
191
|
|
|
192
192
|
## What it asks about
|
|
193
193
|
|
|
194
|
-
Payo understands **
|
|
195
|
-
**TypeScript/JavaScript, Python, Go, Rust, and
|
|
194
|
+
Payo understands **30 frameworks, 29 ORMs, and 17 databases** across
|
|
195
|
+
**TypeScript/JavaScript, Python, Go, Rust, PHP, C#, Java, and Ruby** — and tailors its follow-up
|
|
196
196
|
questions to whatever you pick. Dimensions covered:
|
|
197
197
|
|
|
198
198
|
- **Project** — type (frontend / backend / full-stack / CLI / script) and a short description
|