we previously prepared our sdk to work with Deno. However, using deno deploy (their saas platform) we hit a bug that causes JSON files to error out.
It was caused only when using npm specifiers. However, the alternative of using esm.sh prefix to get the package creates another error
IMO this error doesn't make sense, as it's the same procedures
So, although SDK works with Deno (locally / at chainlink functions), it's not working well with Deno Deploy
needed by @georgeciubotaru at https://github.com/trufnetwork/truf-tradingview-indicators/
we previously prepared our sdk to work with Deno. However, using deno deploy (their saas platform) we hit a bug that causes JSON files to error out.
It was caused only when using npm specifiers. However, the alternative of using esm.sh prefix to get the package creates another error
IMO this error doesn't make sense, as it's the same procedures
So, although SDK works with Deno (locally / at chainlink functions), it's not working well with Deno Deploy
needed by @georgeciubotaru at https://github.com/trufnetwork/truf-tradingview-indicators/