add plu-ts

[michele-nuzzi]

to build yourself just go in the implementations/plu-ts directory and run

npm install
npm run start

this will generate the implementations/plu-ts/out directory with the compiled scripts in binary form.

scripts are plutus v3

[michele-nuzzi]

btw the out directory is already generated if you don't want to bother

[SeungheonOh]

Can you deal with nix as well...? maybe?

[michele-nuzzi]

every time I tried nix I ended up crying in a corner

sorry not used to it

[SeungheonOh]

lol fair enough. @t4ccer do we have enough budget left here do deal with nix?

[t4ccer]

Thank you for contributing, a couple of initial comments:

• Scripts do not deserialize, all complain with Codec.CBOR: deserialising failed at offset 0 : expected bytes. Make sure to serialize them the same way other implementations are doing that (Haskell function is serialiseCompiledCode from PlutusLedgerApi.V2)
• Once Nix work is set up we should not store compilation artifacts in ./out in the repo (I can handle that)
• I'm not sure how implicit data decoding/encoding works in plu-ts but make sure that enums are encoded as integers and structs with only one constructor like a list of fields (no Constr 0), but once you get script serialization fixed the test suite will yell at you
• At the end decide on TS formatter, but later to not cause merge conflicts now
• Announce it in readme section

[t4ccer]

OK, I've fixed the serialization and nixified the whole build. Now you can see that tests are failing due to data decoding, once that is fixed and V2 script context is figured out we should be good to merge. You can run tests locally either with cabal test inside ./tests directory, there you can override UPLC_BENCHMARK_BIN_PLU_TS env var to point it somewhere outside nix sandbox or with just nix build .#checks.x86_64-linux.uplc-benchmark to run it like it'll be ran on CI