-
Notifications
You must be signed in to change notification settings - Fork 186
[core] pnpm migration #1594
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
base: dev
Are you sure you want to change the base?
[core] pnpm migration #1594
Conversation
|
@mattpodwysocki please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
maybe add a new workflow file that runs the new build/tests? |
@mattpodwysocki Love this work! Would be great to have it in - @pelikhan tells me it solves many of the things I've been asking for 😄 |
…naiscript into feat/pnpm-migration
…naiscript into feat/pnpm-migration
…in prompt context
…naiscript into feat/pnpm-migration
Aligned configs, fixed formatting, and modernized dependencies.
The `test` script now uses `vitest --run` for immediate test runs.
…line browser launch process
…runtime" across multiple files
Investigator reportContext collection
AI AnalysisThe root cause of the failure is:
Responsible code: Potential fix: pnpm install This will synchronize Summary: The root cause is an out-of-date
|
This is a refactoring to introduce the following:
@genaiscript/core
@genaiscript/runtime