I am back to looking at this a try to make this make better. After a bit of searching, I realized in put in a project setting to enable this. I should have know this as this is often done for new, experimental features.
Set "feature/process_jsx" to "true". This should enable the custom layout editor to process all javascript as jsx. Not that this should be harmless for all normal js. It will take a little longer to save as the jsx process is not fast, but since TACTIC caches the jsx in the saved custom layout, it will execute fast.
09-09-2021, 06:47 PM (This post was last modified: 09-09-2021, 06:48 PM by listy.)
(09-09-2021, 06:43 PM)remkonoteboom Wrote: Set "feature/process_jsx" to "true". This should enable the custom layout editor to process all javascript as jsx. Not that this should be harmless for all normal js. It will take a little longer to save as the jsx process is not fast, but since TACTIC caches the jsx in the saved custom layout, it will execute fast.
I did this, and double checked this is enabled. But the problem is with my JSX setup. I don't have much time to investigate and searching for the problem, at this time
As i wrote earliet, i think it is babel and npm problem. Even babel executables are lied in different folder than yours