high1
high1
Turns out that the Webpack 5 is coming with integrated types, and that is the issue - the definition for the Resolver type inside the plugin conflicts with the one...
@rsimoes A lot of ecosystem has not caught up with the latest Webpack, so a lot of plugins depend on Webpack 4 types, and it's honestly a mess - not...
Webpack has it's types integrated in version 5, and mixing previous and current types results in a mess, that's why I switched to pure JS for now.
Could you give me a complete repro? I was working on an update, and hoping to push something more substantial in the coming days, after a period of inactivity.
Yes, there's something not working right. I'll fix this as soon as I find some time.
I'll try and see if it works. That being said, I don't see the purpose of the code that does protocol/origin/port checking, since the iframe ends up on the page...
On line 44 `window.parent.postMessage('router_status.asp');` has the origin - so the message doesn't even reach the iframe. I think this could be done using MessageChannel, which would avoid the need to...
@unisoftenterprises I find this "feature" of hiding the iframe very lacking - the full functionality is still fully exposed, it's just that the iframe is hidden. It should be possible...