Ruben Buniatyan
Ruben Buniatyan
@m-ghaoui Yes, but we have to wait until the .NET 7 release as out-of-process Functions are not as feature-rich as in-process ones.
Also, both v1 and v2 don't work for React when react-scripts v5 is used.
@BenGOsborn Yep, I ended up downgrading to react-scripts v4 although that's not the solution I'm looking for.
For `CRA v5`, this can be fixed with [CRACO](https://github.com/gsoft-inc/craco) or [react-app-rewired](https://github.com/timarney/react-app-rewired). In case of CRACO, the `.cracorc.js` should look like ```javascript const { ProvidePlugin } = require('webpack'); module.exports = {...
With the release of .NET 7, we can move to the central package management once the project initial migration is done and dusted.
Given that everything is mobile-first nowadays, it's a pity this issue hasn't been addressed yet. Could this be prioritized, please?
Looks like the non-JNI functions are not exported for Windows.
Any chance this will be addressed in the next release?
@xas Thank you much for the idea. Closing in favor of #5314.
@iSOcH As the old package is now replaced with a new one, we expect this should no longer be an issue. The old one had its versioning wrong; say, instead...