chore(prueba && terminal): update deps

[enzonotario]

Summary by CodeRabbit

• New Features

  • Updated development dependencies for improved performance and features.
  • Incremented version of the xterminal package for potential enhancements.
  • Added Prettier for code formatting consistency across the project.
  • Introduced new test scripts for better testing command management.

• Bug Fixes

  • Minor visual adjustment in code frame output for better readability.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
editor	⬜️ Ignored (Inspect)	Visit Preview		Apr 20, 2025 2:08pm

[coderabbitai[bot]]

## Walkthrough
Se han realizado varias modificaciones en diferentes paquetes. Se actualizó la matriz de versiones de Node.js en el flujo de trabajo de GitHub Actions para pruebas, se corrigió la sintaxis de importación JSON en configuraciones y scripts, se cambió el script de test en el `package.json` raíz para ejecutar pruebas en todos los paquetes, se añadió un nuevo script de test en el paquete CLI, se actualizó la dependencia `xterminal` en el paquete terminal, y se ajustó un test en `esbabel` para usar `mut` en lugar de `var` según la nueva convención de declaración de variables.

## Changes

| Archivos                                               | Resumen del cambio                                                                                                  |
|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
| `.github/workflows/test.yml`                          | Se añadió Node.js 22.x a la matriz de versiones para pruebas en GitHub Actions.                                     |
| `apps/playground/nuxt.config.ts`, `packages/cli/postinstall.js` | Cambio en la sintaxis de importación JSON de `assert { type: 'json' }` a `with { type: 'json' }`.                   |
| `package.json`                                        | Script `"test"` modificado para ejecutar pruebas en todos los paquetes con `pnpm --stream -r run test:run`.         |
| `packages/cli/package.json`                           | Añadido script `"test:run"` que muestra un mensaje de error sin salir con código de fallo.                         |
| `packages/esbabel/test/knownIssues.test.ts`          | En test ignorado, se cambió `var get = 'prueba'` por `mut get = 'prueba'` para reflejar nueva semántica de variables.|
| `packages/terminal/package.json`                      | Actualizada la versión de la dependencia `xterminal` de `^2.0.8` a `^2.1.9`.                                       |

## Poem
> 🐇 En el código saltarín,  
> cambios vienen sin fin.  
> De `var` a `mut` en el lugar,  
> nuevas versiones a instalar.  
> Pruebas corren sin cesar,  
> y JSON importa al pasar.  
> ¡Así en el código vamos a brillar! 🌿✨

[!TIP]

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

✨ Finishing Touches

• [ ] 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.