Gerald
@da2x thanks for the detailed analysis. You are right about the defect. We have a plan to improve the process by implementing a new flow: https://github.com/violentmonkey/violentmonkey/discussions/1529 with remote locking +...
Sounds reasonable, but I guess that's a big step.
> The options.html page opens but doesn't progress after the first batch of canRender :-) I'm looking into it, might be due to some objects not `reactive`.
> I see that sourcemaps are completely wrong: it counts from the first line of the .vue file instead of the actual line 38. Indeed. I found a workaround by...
I think it's related to our configuration. Only files under `src/common/ui` are affected. The issue is gone if I copy the same file to another directory, e.g. copy `src/common/ui/code.vue` to...
I think it has nothing to do with ``. All components in `src/common/ui` have incorrect source maps. It works if I move the file out of that directory without touching...
It seems to be `FakeDepLoader` that messes the sourcemap up.
The tests failed because of jest, let me fix it.
I think this could be a Chrome issue, it happens on latest Chrome (106) and Edge (Chrome 105), but not on Firefox and Vivaldi (Chrome 104). Not sure what is...
It seems to be vueleton compiled targeting newer browsers. Let me fix it.