:memo: fix TextEditor::delete() doc
Throw on non-release builds if translating positions on destroyed editor

It’s possible that bundled packages stray into this corner case, so I’d
like us to catch and fix misbehaving packages before exposing users to 
any exceptions. Once we go one release with this turned on, we can
enable the exception for all builds.
:penguin: Add troubleshooting for system gyp error

Closes #2824
:arrow_up: language-php@0.17
Merge pull request #3965 from brunetton/master

:memo: fix TextEditor::delete() doc
:arrow_up: language-sass@0.24
:arrow_up: atom-light-syntax@0.21
:arrow_up: atom-dark-syntax@0.20
Merge pull request #3974 from atom/ns-throw-on-destroyed-editors

Throw on non-release builds if translating positions on destroyed editor
:arrow_up: markdown-preview@0.106
Assign pane container before emitting onDidAddPane events

Fixes #3972
:memo: Mention profile picture
:arrow_up: language-coffee-script to fix jasmine snippet quotes
Upgrade to bracket-matcher@0.62
Clear focused window property on window closed

Closes #3806
Update Tokenized/DisplayBuffer prior to TextBuffer::onDidChange handlers

Fixes #3789
:arrow_up: language-ruby@0.41
Unmount TextEditorComponent when TextEditor is destroyed

We don’t want to do it when the element is detached because it might
be caused by moving the editor rather than destroying it. Unmounting
the component entirely and then remounting it causes the hidden input
to not be recycled, interfering with focus restoration. Watching for
destruction of the model is a good way to ensure we always tear down
the view at the right time without doing it prematurely.
Call legacy SpacePen remove hooks before unmounting TextEditorComponent
Prepare 0.141