Contributing

We’re happy to accept contributions — whether it's bug fixes, features, docs, or language SDKs.
Typenv aims to be language‑agnostic and grow beyond just JavaScript or TypeScript.

---

How to Contribute

1. Fork the repo and create a new branch.
2. Make your changes in the relevant folder (e.g. apps/, packages/, or sdk/go/).
3. Test locally and commit with a clear message.
4. Open a pull request with context and examples if needed.

---

Repo Structure

---

📦 SDK Naming

If you're building a new SDK (e.g. for Go, PHP, or Python),
please use the package name typenvx or a consistent variation like:

• typenvx-go
• @typenvx/sdk-rust
• typenvx_php

Keeping a unified naming scheme helps discoverability and avoids fragmentation.

---

Issues

Please use

GitHub Issues

for bugs, feature requests, or general questions.

---

Thanks

Every contribution helps make Typenv better.
Whether you're fixing typos or building a full SDK — we appreciate it.