Skip to content

Conversation

andersk
Copy link
Contributor

@andersk andersk commented Jul 8, 2021

Fixes #878, fixes #998.

@andersk andersk force-pushed the promise-types branch 2 times, most recently from d54b176 to fb20c86 Compare July 8, 2021 22:41
@andersk andersk mentioned this pull request Jul 8, 2021
@VerteDinde
Copy link
Collaborator

@andersk Sorry it took so long for someone to see this 🙂 I merged your doc/type PR and I think I can reconcile the conflicts in the main definition file, but let me know if that seems reasonable and we can merge this one as well!

@andersk
Copy link
Contributor Author

andersk commented Sep 16, 2021

The PR you merged (#897) is not mine. Like I said there, this is a more complete fix. It was was intended to be merged instead of #897, not in addition to #897.

However, I’ve now resolved the conflicts so this can be applied on top.

@jlennox
Copy link

jlennox commented Jan 11, 2022

@andersk @VerteDinde Is there any update on this?

This would presumably fix an issue I am seeing:

.../node_modules/spectron/lib/spectron.d.ts:260:24 - error TS2694: Namespace 'Electron.CrossProcessExports' has no exported member 'RemoteMainInterface'.

260     electron: Electron.RemoteMainInterface;
                           ~~~~~~~~~~~~~~~~~~~

‘declare module’ is for declaring a third-party module, not for
publishing first-party declarations.

Signed-off-by: Anders Kaseorg <andersk@mit.edu>
Fixes electron-userland#878, fixes electron-userland#998.

Signed-off-by: Anders Kaseorg <andersk@mit.edu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing Promise for {electron, browserWindow, webContents} types Wrong typing of Application.electron on Spectron 13.0.0
3 participants