Currently pkl-typescript doesn't depend on @pkl-community/pkl, which means the user can choose what underlying version of Pkl they want to use. However, that means pkl must be installed on the host.
If we make @pkl-community/pkl a peerDependency, and use it in the evaluator by default, we could get a much nicer "first-run" experience - ideally npm install @pkl-community/pkl-typescript @pkl-community/pkl would work out-of-the-box with no other host dependencies. Users could still override the PKL_EXEC env var to use a custom binary.
Currently
pkl-typescriptdoesn't depend on@pkl-community/pkl, which means the user can choose what underlying version of Pkl they want to use. However, that meanspklmust be installed on the host.If we make
@pkl-community/pkla peerDependency, and use it in the evaluator by default, we could get a much nicer "first-run" experience - ideallynpm install @pkl-community/pkl-typescript @pkl-community/pklwould work out-of-the-box with no other host dependencies. Users could still override thePKL_EXECenv var to use a custom binary.