Complete repository conversion from what-the-fetch to format-prompt (#3)

* Initial plan

* Update package.json and create tests for format-prompt

Co-authored-by: hckhanh <6380436+hckhanh@users.noreply.github.com>

* Update documentation for format-prompt

Co-authored-by: hckhanh <6380436+hckhanh@users.noreply.github.com>

* Update all remaining what-the-fetch references to format-prompt

Co-authored-by: hckhanh <6380436+hckhanh@users.noreply.github.com>

* Update dependencies and improve whitespace handling in prompt

* Add tests for tab-based code indentation

Co-authored-by: hckhanh <6380436+hckhanh@users.noreply.github.com>

* Remove dependency optimization step from autofix.yml

* Update dependencies to latest versions

* Update autofix.yml to use 'bun format' for code formatting

* Update autofix.yml to install dependencies and change formatting command

* [autofix.ci] apply automated fixes

* Update src/index.ts

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Update test/prompt.test.ts

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Fix grammar errors and update SECURITY.md for format-prompt

Co-authored-by: hckhanh <6380436+hckhanh@users.noreply.github.com>

* Add changeset for repository conversion

Co-authored-by: hckhanh <6380436+hckhanh@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: hckhanh <6380436+hckhanh@users.noreply.github.com>
Co-authored-by: Khánh Hoàng <hi@khanh.id>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: 4 people

.changeset/config.json

@@ -7,5 +7,5 @@
   "access": "restricted",
   "baseBranch": "main",
   "updateInternalDependencies": "patch",
-  "ignore": ["what-the-fetch-docs"]
+  "ignore": ["format-prompt-docs"]
 }

.changeset/thirty-meals-feel.md

@@ -0,0 +1,5 @@
+---
+"format-prompt": patch
+---
+
+Complete repository conversion from what-the-fetch to format-prompt. This is a new library for formatting prompts for LLMs with optimal token usage.

.github/PULL_REQUEST_TEMPLATE.md

@@ -4,7 +4,7 @@
 
   Before submitting a pull request, please make sure the following is done:
 
-  1. Fork [the repository](https://github.com/hckhanh/what-the-fetch) and create your branch from `main`.
+  1. Fork [the repository](https://github.com/hckhanh/format-prompt) and create your branch from `main`.
   2. Run `npm install` in the repository root.
   3. If you've fixed a bug or added code that should be tested, add tests!
   4. Ensure the test suite passes (`npm test`).

.github/copilot-instructions.md

@@ -1,8 +1,8 @@
-# Copilot Instructions for what-the-fetch
+# Copilot Instructions for format-prompt
 
 ## Project Overview
 
-This is **what-the-fetch**, a type-safe API client library with schema validation using Standard Schema. The project provides end-to-end type inference for API requests and responses, integrating with popular schema validation libraries like Zod, Valibot, and ArkType.
+This is **format-prompt**, a utility library for formatting prompts for cleaner presentation and optimal token usage. The project removes unnecessary whitespace and line breaks while preserving the intended structure of prompts.
 
 ## Installation & Setup
 
@@ -42,29 +42,28 @@ npm run format
 ### Testing
 - Tests are located in the `test/` directory
 - Use Vitest as the test framework
-- Mock external dependencies (e.g., `global.fetch`)
 - Test file naming: `*.test.ts`
 - Include tests for:
   - Happy paths
-  - Error cases
   - Edge cases
-  - Type safety validations
+  - Whitespace handling
+  - Interpolation
 
 ## Project Structure
 
 ```
 src/
-  ├── index.ts       # Main export and createFetch function
-  ├── types.ts       # Type definitions
-  └── utils.ts       # Utility functions (e.g., validation)
+  └── index.ts       # Main export and prompt function
 test/
-  └── createFetch.test.ts  # Test suite
+  └── prompt.test.ts # Test suite
+benchmark/
+  └── prompt.bench.ts # Benchmarks
 ```
 
 ## Key Dependencies
 
-- **@standard-schema/spec**: Standard Schema specification for validation
-- **fast-url**: URL building and parameter substitution
+- **string-collapse-leading-whitespace**: Collapse leading whitespace
+- **string-collapse-white-space**: Collapse general whitespace
 - **vitest**: Testing framework
 - **biome**: Linting and formatting
 - **tsdown**: TypeScript bundler powered by rolldown
@@ -111,15 +110,15 @@ The CLI will ask you:
 - **Be descriptive**: Write summaries that explain what changed and why
 - **Include examples**: For new features, include code examples in the changeset
 - **One changeset per PR**: Generally, create one changeset per pull request
-- **Edit the changeset file**: After creation, you can manually edit `.changeset/*.md` to add more details, examples, or formatting
+- **Edit the changeset file**: After creation, you can manually edit `.changeset/*.md` to add more details
 
 ### Changeset File Format
 
 Changesets are stored in `.changeset/*.md` files with the following format:
 
 ```markdown
 ---
-"what-the-fetch": minor
+"format-prompt": minor
 ---
 
 Brief summary of the change
@@ -131,21 +130,20 @@ More details, code examples, migration guides, etc.
 
 ## API Design Principles
 
-- **Type Safety First**: All APIs must provide full type inference
-- **Standard Schema Compatible**: Work with any schema library implementing Standard Schema
-- **Minimal Surface Area**: Keep the API simple and focused
+- **Simplicity First**: The API should be simple and intuitive
+- **Template Literal Support**: Work seamlessly with JavaScript template literals
+- **Minimal Surface Area**: Keep the API focused on one thing - formatting prompts
 - **Zero Breaking Changes**: Maintain backward compatibility
 - **Bundle Size**: Keep dependencies minimal and bundle size small
 
 ## Common Tasks
 
 ### Adding a New Feature
-1. Define types in `types.ts` if needed
-2. Implement functionality in `index.ts` or `utils.ts`
-3. Add JSDoc comments with examples
-4. Write comprehensive tests
-5. Update README.md if adding public APIs
-6. Add a changeset with `npx changeset add` (select "minor")
+1. Implement functionality in `src/index.ts`
+2. Add JSDoc comments with examples
+3. Write comprehensive tests
+4. Update README.md if adding public APIs
+5. Add a changeset with `npx changeset add` (select "minor")
 
 ### Fixing a Bug
 1. Write a failing test that reproduces the bug
@@ -165,6 +163,4 @@ More details, code examples, migration guides, etc.
 - This project uses **Bun** in CI but supports all package managers
 - The package is published to both npm and JSR (Deno)
 - The library must remain framework-agnostic
-- Response validation happens automatically when schemas are provided
-- Default method is GET; POST is used when body is present
-- Custom headers merge with default headers (Content-Type: application/json)
+- The function uses string manipulation utilities for optimal performance

.github/workflows/autofix.yml

@@ -25,8 +25,8 @@ jobs:
         uses: SocketDev/action@4337a545deecc20f19a909e52db7a2f6ba292f42 # v1.2.0
         with:
           mode: firewall
-      - name: Optimize dependencies with @socketregistry overrides
-        run: socket optimize
+      - name: Install dependencies
+        run: sfw bun install
       - name: Format code
         run: bun biome check --write
       - name: Fix package.json

SECURITY.md

@@ -11,7 +11,7 @@ We release patches for security vulnerabilities. Currently supported versions:
 
 ## Reporting a Vulnerability
 
-We take the security of what-the-fetch seriously. If you believe you have found a security vulnerability, please report it to us as described below.
+We take the security of format-prompt seriously. If you believe you have found a security vulnerability, please report it to us as described below.
 
 ### Please do NOT:
 
@@ -41,23 +41,21 @@ Please include the following information in your report:
 
 ## Security Best Practices
 
-When using what-the-fetch in your applications:
+When using format-prompt in your applications:
 
-1. **Keep Dependencies Updated**: Regularly update to the latest version of what-the-fetch to receive security patches
-2. **Input Validation**: Always validate user input before passing it to API calls, even with schema validation enabled
-3. **Use TypeScript**: Take advantage of TypeScript's type safety to catch potential issues at compile time
-4. **Schema Validation**: Ensure your schemas properly validate all response data to prevent unexpected data from being processed
+1. **Keep Dependencies Updated**: Regularly update to the latest version of format-prompt to receive security patches
+2. **Use TypeScript**: Take advantage of TypeScript's type safety to catch potential issues at compile time
+3. **Sanitize Interpolated Values**: Be cautious when interpolating user-provided values into prompts to prevent prompt injection attacks
 
 ## Scope
 
 The following are considered in scope for security reports:
 
-- Schema validation bypass vulnerabilities
 - Type safety violations
-- URL injection vulnerabilities
-- XSS vectors through API responses
-- Data leakage through improper validation
-- Any behavior that could lead to security issues in applications using what-the-fetch
+- String manipulation vulnerabilities that could lead to prompt injection
+- XSS vectors through improper string handling
+- Data leakage through template literal interpolation
+- Any behavior that could lead to security issues in applications using format-prompt
 
 ## Out of Scope
 
@@ -82,4 +80,4 @@ For any questions about this security policy, please contact: hi@khanh.id
 
 ## Learn More
 
-For general bugs and feature requests, please use our [GitHub Issues](https://github.com/hckhanh/what-the-fetch/issues).
+For general bugs and feature requests, please use our [GitHub Issues](https://github.com/hckhanh/format-prompt/issues).