JavaScript/Typescript implementation

[fabiofranzini]

Hi, do you have a public plan to add the JavaScript / Typescript implementation of Power FX language and runtime?
It would be fine to have the current C# implementation that compiles the functions to js

[MikeStall]

That's definitely on the roadmap.
PowerApps consumes the PowerFx.Core package from this repo for parsing and binding. But instead of consuming the interpreter here, it has an alternative Power Fx backend (written in C#) that compiles to JScript. We would like to open source the JS implementation, but no ETA yet.

We also have a 3rd backend that compiles to SQL - it is used for formula columns. We'd also like to open source that.

[YousefED]

Hi @MikeStall ! Is this still on the roadmap? Would love to embed PowerFx in a javascript app!

[cchannon]

I'll toss in a vote for the same. While having a server context like Blazor to interact with is a technically viable option, it is also not very "Power Platform." An approach like that can't be deployed in a solution, it introduces release and configuration management headaches, and it can mean a lot of overhead to deploy securely, whereas if the eval happens only client-side those concerns pretty much evaporate.

[fabiofranzini]

Yes @cchannon but you can use Blazor not in the server context but into the client context.
This, while feasible, does not appeal to me because it still requires loading the Blazor runtime in addition to the PowerFx runtime. The best thing would be to have PowerFx's functions and runtime compiled directly into javascript

[MikeStall]

This is still on the roadmap, but no ETA.

For now, your best bet is still blazor / wasm - there is an example here: #140
PVA just went into public preview using wasm.

The goal is that Power Fx is fully bundled with Power Platform, so you don't have to deploy it. For example, Power Fx is already being used in UCI and forms for Commanding - we don't want to load a 2nd JScript Power Fx runtime for the solution.

[YousefED]

Thanks for the quick replies. My use-case is to use it as a scripting system outside of the Power Platform. The wasm implementation is interesting, but not really feasible (20mb, etc). Looking forward to the JS / TS version!

Is Power Platform internally using a Javascript version? Or a cross-compiled / wasm solution?

[filcole]

I will write a blog on how to do this by using a Custom API in the Power Platform. It's still a bit of hack until it's fully deployed (and uses preview features).

…

On Fri, 11 Nov 2022, 17:09 Mike Stall, ***@***.***> wrote: This is still on the roadmap, but no ETA. For now, your best bet is still blazor / wasm - there is an example here: #140 <#140> PVA just went into public preview using wasm. The goal is that Power Fx is fully bundled with Power Platform, so you don't have to deploy it. For example, Power Fx is already being used in UCI and forms for Commanding - we don't want to load a 2nd JScript Power Fx runtime for the solution. — Reply to this email directly, view it on GitHub <#384 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOL7PULMZ3A7GHI236ZPCLWHZ4V5ANCNFSM5VR4ROHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[BetimBeja]

if you mean the blogpost from @filcole you can find it here https://philcole.org/post/powerfx-customapi/

[rogerhendriks]

Sorry wrong thread :)

[rogerhendriks]

@MikeStall hi, any update on the JavaScript / TypeScript status?

[MikeStall]

sorry, not yet. Primary focus has been on C# interpreter to enable PVA, Cards, Datavverse Plugins (more at #1529)