Closed MarshallOfSound closed 7 years ago
This is still on my list
I'm gonna merge this for now so that it doesn't get paved when I convert electron-compile to TypeScript
Where would one include this? I'm including it in one of my scripts, but I assume it needs to be located in a forge or compile script somewhere?
Where would one include this? I'm including it in one of my scripts, but I assume it needs to be located in a forge or compile script somewhere?
I put in in index.ts but I don't think it matters so much. As far as I can tell it just has to be executed before any files needing the bypass are loaded.
Fixes https://github.com/electron-userland/electron-forge/issues/153
The reason I added this instead of a new
bypass://
protocol or similar is because (on windows at least) the file path passed to the Electron protocol handler only works as expected onfile://
not on any other URI's, it just get's completely messed up. This would seem to achieve what the above issue needs to so I think it's good enough for now :+1:.Users can now just do this.
Or something similar, the more common use case might be a function like this (untested).
Which would theoretically bypass
electron-compile
for all files not in the current app.