httpYac (current version 6.16.7) is a robust command-line interface (CLI) and Node.js package designed for testing and automating API interactions using `.http` and `.rest` files. It supports an extensive range of protocols including HTTP, REST, GraphQL, WebSocket, gRPC, RabbitMQ (AMQP), EventSource, and MQTT, offering a versatile solution beyond traditional HTTP-only clients. The project maintains an active development pace, with frequent minor releases (e.g., 6.16.x) primarily focusing on bug fixes, performance improvements, and feature enhancements, as demonstrated by its detailed changelog entries. Its core strength lies in enabling developers to define complex request sequences, variables, and test assertions directly within `.http` files, providing a file-based alternative to GUI tools like Postman or Insomnia. A key differentiator is its extensibility and the fact that it ships with comprehensive TypeScript types, facilitating programmatic integration despite its primary CLI orientation. It requires Node.js version 18 or higher to run effectively, ensuring compatibility with modern JavaScript runtime features. The tool also boasts a popular VS Code extension, making it a powerful choice for developers working within that ecosystem.
npm install httpyacVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to create a basic `.http` file with variables and multiple requests, and then execute it programmatically using the `httpyac` library in a TypeScript environment, logging the results.
Review all test suites utilizing `@ref` directives. Modify dependent requests or test logic to explicitly check the results of referenced requests if their success is critical for subsequent steps, as the execution flow may no longer halt automatically.
Ensure that all tests within a request region succeed if subsequent requests or scripts depend on variables derived from its named response. Update test assertions to pass consistently or refactor dependencies.
For complex programmatic use, consult the TypeScript declaration files (`.d.ts`) or the project's source code to understand available APIs. For simpler automation, consider executing the CLI directly using Node.js's `child_process` module.
Only use `--insecure` for development or testing with self-signed certificates in controlled environments. For production, ensure target servers use valid, trusted SSL certificates, or properly configure your Node.js environment to trust custom Certificate Authorities.
Refer to the `httpyac` documentation for the exact variable resolution order. For highest precedence in CLI calls, use the `--var` flag. For programmatic usage, ensure your `environments` object is structured clearly and accounts for potential overrides.
Install `httpyac` globally using `npm install -g httpyac` (or `yarn global add httpyac`). Verify that your npm/yarn global bin directory is correctly added to your system's PATH.
Install `httpyac` as a local project dependency: `npm install httpyac` or `yarn add httpyac`.
Review the specified line number and the surrounding content in your `.http` file. Consult the `httpyac` documentation (or the IntelliJ HTTP Client specification which it largely follows) for correct syntax rules.
For development or testing purposes, you can use the `--insecure` flag with the CLI (`httpyac send --insecure ...`) or set `insecure: true` in programmatic options. For production or secure environments, ensure the server has a valid, publicly trusted SSL certificate, or configure Node.js to explicitly trust your custom CA certificate.
This specific issue (when the state parameter is percent-encoded) was fixed in `httpyac v6.16.7`. Ensure you are using `httpyac@6.16.7` or a newer version. If the problem persists, review your OAuth2 provider's configuration and ensure callback URLs are correctly configured and match.
No dependency data recorded yet.