You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm developing a NW.JS application using GWT. The applicaton needs access to node.js methods to work. I've found no way to point nw to load my application via SuperDevMode in such a way that it'd give access to node.js functionality for my application. Apparently, this was actively blocked out as a security hole per ticket #534.
My current workaround is to debug all non-filesystem related issues using SuperDevMode and a web browser, and then just crank out build after build using the regular GWT compiler to test with nw.js, but this is cumbersome.
I'd like nw.js to provide a command-line switch for these situations, to grant a security exception to an application loaded via a specific (perhaps even just localhost) URL.
For the record, SuperDevMode provides an up-to-date application via http://localhost:8888/ by default (recompiled on reload if necessary), although it's configurable.
I'm developing a NW.JS application using GWT. The applicaton needs access to node.js methods to work. I've found no way to point nw to load my application via SuperDevMode in such a way that it'd give access to node.js functionality for my application. Apparently, this was actively blocked out as a security hole per ticket #534.
My current workaround is to debug all non-filesystem related issues using SuperDevMode and a web browser, and then just crank out build after build using the regular GWT compiler to test with nw.js, but this is cumbersome.
I'd like nw.js to provide a command-line switch for these situations, to grant a security exception to an application loaded via a specific (perhaps even just localhost) URL.
For the record, SuperDevMode provides an up-to-date application via http://localhost:8888/ by default (recompiled on reload if necessary), although it's configurable.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: