types / env-electron Goto Github PK

My code is:

import { BrowserWindow } from 'electron'

function doSomeOnWindow(win: BrowserWindow) {
  win.loadURL('...')
}

It is wrong:

error TS2304: Cannot find name 'BrowserWindow'

So how do I correct it?

https://github.com/typed-typings/env-electron/blob/master/index.d.ts#L1-L6

Relevant changelog notes:

• commit Add isMainFrame parameter to did-fail-load event of WebContents.
• commit Add statusLine property to webRequest.OnHeadersReceived API's responseHeaders object.
• commit Add backgroundThrottling option to webPreferences of BrowserWindow.
• commit Add resourceType parameter to did-get-response-details event of WebContents.

https://github.com/typed-typings/env-electron/blob/master/index.d.ts#L4226-L4228. I can't see any actual value coming from that, and I feel like it's very brittle - the users node typings may not have this interface exposed ambiently.

I ran typings install env~electron but got not found error

typings ERR! message https://api.typings.org/entries/npm/env~electron responded with 404, expected it to equal 200

typings ERR! cwd /Users/xxxxxxx
typings ERR! system Darwin 15.6.0
typings ERR! command "/Users/xxxxxx/.nvm/versions/node/v5.0.0/bin/node" "/usr/local/bin/typings" "info" "env~electron"
typings ERR! node -v v5.0.0
typings ERR! typings -v 0.7.12
typings ERR! code EINVALIDSTATUS

It's currently specified as any.

Documentation: http://electron.atom.io/docs/v0.37.6/api/session/#seswebrequest

@unional Are you still using this? I noticed some updates have some through DefinitelyTyped by @miniak - see https://github.com/DefinitelyTyped/DefinitelyTyped/commits/master/github-electron/github-electron.d.ts. @miniak Is there anything we can do to help you perhaps?

Related to typings/registry#980

Electron is working on providing an official electron.d.ts (automatically generated from the API docs) electron/electron#4875. Please raise any concerns / ideas there.

This copy is very badly outdated and should not be used.

This one is tricky, but generally valuable. Currently the type definition is directly tied to the current Node.js type definition shape on DefinitelyTyped. I'd love to move away from relying on ambient shapes and instead rely on the actual exposed types. E.g. Change from relying on NodeJS.EventEmitter to import { EventEmitter } from 'events'. Basically, making dependencies explicit and mirroring what exists at runtime instead of relying on implicit and ambient interfaces.