Vahor/n8n-kit

AI Summary: The user requests two enhancements for the `n8n-kit` project. First, to modify the `--version` CLI output to include the `n8n-kit` version, `n8n` version, and potentially the `n8n-core` version. Second, to add a dynamic badge to the README, using `shields.io`, that displays the currently supported `n8n` version.

AI Summary: This issue requests adding a specific warning message when a user attempts to use a TypeScript (`.ts`) file as an entrypoint with a Node.js version older than 22.18. The goal is to replace the generic "Unknown file extension" error with a more helpful message, guiding users to upgrade Node.js or use Bun.

AI Summary: This issue proposes adding support for community nodes, but the current assessment suggests that users can already achieve this by extending the existing `Node` class. The primary task is to document this process in the README, explaining how to create and configure custom node types.

AI Summary: This issue proposes creating a new type utility and a corresponding helper method to simplify handling a union type `ExpressionBuilder<any, any, X> | X`. The goal is to reduce repetitive `if` conditions by providing a single method that can extract the `X` value, either directly or by calling `toExpression()` on the `ExpressionBuilder` instance. This enhancement aims to improve code readability and maintainability.

AI Summary: The `outputSchema` property in `n8n-kit` is currently only used for type definition and does not perform runtime validation. This issue proposes adding JSDoc comments to the `outputSchema` definition and a clarifying message in the `README.md` to explicitly state its purpose as a typedefinition, preventing user confusion.

AI Summary: This issue proposes automating the weekly generation of n8n nodes using a GitHub Action. The process involves updating a submodule, running a generation command, committing the changes, adding a changeset, and creating a pull request. It also requires logic to close any existing pull requests created by this automation before opening a new one.

AI Summary: This issue proposes introducing an `ImportedWorkflow` class (or similar construct) to enhance type inference when using the `ExecuteWorkflow` node. Instead of directly passing a `workflowId`, users could define an `ImportedWorkflow` instance with explicit input and output schemas, which the `ExecuteWorkflow` node would then accept for improved type checking. This imported workflow would serve purely for type inference and not be part of the application's build or deployment.

AI Summary: This issue addresses a problem where multiple projects deploying to the same n8n instance can overwrite each other's workflows if they share identical workflow IDs, due to the same hashId generation. The proposed solution is to incorporate a unique project identifier (like a UUID from a config file or the `package.json` name as a fallback) into the workflow hash generation process to ensure unique hashIds across different projects.

AI Summary: This issue requests a new CI check for the `n8n-cli import` command. The check involves building a workflow, importing its JSON, rebuilding, and then diffing the two JSON outputs to ensure they are identical. A known challenge is that the import command may not correctly generate node versions for all workflows, requiring specific handling.

AI Summary: This enhancement requests adding default values for `sendBody`, `sendHeaders`, and `specificBody` within the `HttpRequest` node in the `n8n-kit` project. Specifically, if `jsonBody` is present, `sendBody` should default to `true` and `specificBody` to `'json'`. If `headerParameters` are set, `sendHeaders` should default to `true`, with all defaults only applying if the respective values are currently undefined.

AI Summary: The `packages/n8n-kit/test` directory and its contents are currently committed but are only used for generating a few nodes. The issue proposes to remove this folder from the repository to avoid confusion, instead generating its content on the fly at the beginning of the relevant script and deleting it afterwards.