Can I use php-wasm in production in near future?

[mschop]

Hi,

I have a rule engine written in PHP that we currently only run on the server side. In future I need this rule engine to work offline in a web view based mobile app.

Instead of rewriting the rule engine in JS/TS, I thought about using php-wasm instead. In theory I could then stick to PHP and run the rule engine inside the browser / mobile app.

php-wasm is still alpha, so it seems not quite suitable for a "real" production ready application.

So my questions are:

• Would you recommend using php-wasm in production now or in the near future?
• When and under what conditions are you tagging php-wasm as beta or stable?
• If this rule engine does not require any php extensions, would you say it's save to use php-wasm now? (pure implementation without any side effects)

Thanks in advance!

Best Regards
mschop

[mschop]

One additional comment: I wasn't able to find anything about the stability / future plans in this project. Maybe it would make sense to add a chapter in the README.md reagarding stability / roadmap etc.

[kazzkzpk]

@mschop I've been using it (8.3) in production for +/- 1 year.

I need to make some configurations to fetch elements and execute querySelectors correctly in the frontend and I created a method that simulated Guzzle using fetch, but that's it.

So far, no problems.