First off, thank you for considering contributing to DevUtils for VS Code by Techwasti Infotech! It's people like you that make open source such a great tool for developers.
This project and everyone participating in it is governed by the Code of Conduct. By participating, you are expected to uphold this code.
Before creating bug reports, please check existing issues as you might find that you don't need to create a new one.
When creating a bug report, please include as much detail as possible:
- A clear descriptive title.
- Steps to reproduce the issue.
- Expected behavior vs actual behavior.
- VS Code version and OS platform.
- Any error output or screenshots.
We are always eager to include more developer utilities! If there is a tool you miss in your offline daily workflow, open an issue using the Feature Request template:
- Explain why this enhancement would be useful.
- Provide examples of input and expected output.
- Link any standards or RFCs if applicable (e.g. UUID, JWT, Base64).
- Fork the repo and create your branch from
main. - Install dependencies:
npm install - If you've added code that should be tested, add tests.
- Ensure the test suite passes:
npm test - Run linting checks:
npm run lint - Issue that pull request!
- Zero-Telemetries & Offline-First: DevUtils is strictly an offline utility suite. Do not introduce network calls for processing user data. All parsing, hashing, conversion, and decoding must happen locally in memory.
- Privacy First: Sensitive data like JWTs, private keys, or credentials must never leave the user's machine.
- Commit Standards: Use concise, conventional commit messages (
feat: ...,fix: ...,docs: ...,test: ...).
Feel free to open a discussion or reach out to us at techwastiinfotech@gmail.com.