Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move system prompts to .mts #1170

Open
pelikhan opened this issue Feb 22, 2025 · 1 comment
Open

Move system prompts to .mts #1170

pelikhan opened this issue Feb 22, 2025 · 1 comment

Comments

@pelikhan
Copy link
Member

To leverage runtime, move out of eval.

Copy link

The suggestion to move system prompts to .mts files is an interesting approach, particularly in the context of leveraging modern JavaScript features like runtime compilation and the top-level await syntax. This would allow for a more efficient execution model compared to using eval, which can be computationally expensive and potentially dangerous if not handled properly.

However, it's crucial to evaluate the broader implications of this change:

  1. Compatibility: Ensure that any users or environments that depend on current system prompts are compatible with .mts files.
  2. Testing: Thoroughly test the new implementation to ensure all functionality remains intact and no regressions occur.
  3. Documentation: Update documentation to reflect the new file format and any changes in how system prompts should be managed.

In summary, while moving system prompts to .mts files could offer performance benefits, it must be done with careful consideration of compatibility, testing, and documentation updates to avoid potential issues for existing users.

AI-generated content by issue-reviewer may be incorrect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant