Can you help to upgrade this library to latest ace-build

[wuseal]

Currently, I tried your lib, but the build failed, maybe it's too long time no update, can you help to update it, my requirement is to use JSON mode to hight light JSON editor, Thank you

[daemontus]

Hi! It's probably quite outdated by now, so that is indeed likely the reason why it doesn't work... I can try to update it, but unfortunately I have a rather full schedule in September so I can't promise to do it any time soon :( However, if you are ok with waiting a bit I will try to fix it as soon as I can :)

[wuseal]

Yes of course will waiting for your update 😀

[wuseal]

HI, how is it going on, any plans?

[daemontus]

Hi! I gave it a few hours today. Unfortunately, it seems to be quite a bit of work, because the Kotlin2JS and KotlinFrontend plugins are dead and the whole toolchain moved from npm and webpack 3 (I think?) to yarn and webpack 5. So just about everything that could break breaks.

The good news is that on the current master, the web component works: You can run the demo-web project and hopefully should get an Ace editor with working syntax highlighting.

The bad news is that the worker component is still rather broken and I haven't touched a Kotlin/JS project in years, so I'm not quite sure how to work with it at this point. There are two issues:

1. We are using the target=webworker property in webpack to dynamically load the appropriate ace code depending on whether we are running web or webworker content. However, webpack 5 is doing something weird with the target property: every other value that I tried (e.g. node) is propagated correctly, but webworker is always turned into web. So there's no way to distinguish which resource should be loaded.
2. Right now, there is a static class-loader.js file in the worker module which was extracted from the ace codebase and contains the code necessary to run a worker. With the old plugins, this file was directly visible to the webpack process and could be resolved using its path. However, the latest buildtools do not do this. I am not quite sure how to "propagate" the file to the downstream modules so that they can use it as the "core" JS file of the Ace worker :/

If anyone has any idea of how to resolve this, I'd be happy to hear it :)