| .github | ||
| .vscode | ||
| public | ||
| scripts | ||
| src | ||
| .eslintrc-auto-import.json | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| .nvmrc | ||
| .prettierrc | ||
| .versionrc | ||
| auto-imports.d.ts | ||
| CHANGELOG.md | ||
| components.d.ts | ||
| Dockerfile | ||
| env.d.ts | ||
| index.html | ||
| LICENSE | ||
| nginx.conf | ||
| package.json | ||
| pnpm-lock.yaml | ||
| README.md | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.vite-config.json | ||
| tsconfig.vitest.json | ||
| unocss.config.ts | ||
| vercel.json | ||
| vite.config.ts | ||
Useful tools for developer and people working in IT. Have a look !.
Functionalities and roadmap
Please check the issues to see if some feature listed to be implemented.
You have an idea of a tool? Submit a feature request!
Self host
Self host your own version of it-tools in your homelab with docker:
docker run -d \
--name it-tools \
--restart unless-stopped \
-p 8080:80 \
corentinth/it-tools:latest
Contribute
Recommended IDE Setup
VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).
Type Support for .vue Imports in TS
TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue types.
If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:
- Disable the built-in TypeScript Extension
- Run
Extensions: Show Built-in Extensionsfrom VSCode's command palette - Find
TypeScript and JavaScript Language Features, right click and selectDisable (Workspace)
- Run
- Reload the VSCode window by running
Developer: Reload Windowfrom the command palette.
Project Setup
pnpm install
Compile and Hot-Reload for Development
pnpm dev
Type-Check, Compile and Minify for Production
pnpm build
Run Unit Tests with Vitest
pnpm test
Lint with ESLint
pnpm lint
Create a new tool
To create a new tool, there is a script that generate the boilerplate of the new tool, simply run:
pnpm run script:create-new-tool my-tool-name
It will create a directory in src/tools with the correct files, and a the import in src/tools/index.ts. You will just need to add the inported tool in the proper category and develop the tool.
Credits
Coded with ❤️ by Corentin Thomasset.
This project is continuously deployed using vercel.com.
License
This project is under the GNU GPLv3.