The portal has been updated to allow the user to select the build presets. These populate the app locaiton, api location, and the app artifact location. see below for details

cc @fiveisprime as per our conversation

otherwise, even with a small repo, the "skip for now" may be after 20 or 30 items. The user may not scroll that far and may never see it as an option.

@fiveisprime

Some thoughts on basic mode:

shortest possible flow, IMO:

1. github repo URL (covers org, repo, even branch if they include it)
2. app location ( we can scan the repo for app, and suggest, but we should not choose it IMO)

I really like not having to enter or and repo separately. GH users are very familiar, I argue, with copying and pasting a GH url. And avoiding two prompts for one ... I think is worth considering. I don't have a problem with the two prompts if you see fit to keep it, but I wanted to toss this up there.

name ... we dont have to ask them for a name. we can give it a name based on the funky name of the SWA URL. WHy not? For basic wizard it would eliminate yet another step. And make it easier to relate the resource to the URL.

app artifact location This folder is different based on the web framework. That's why it must be filled in by the user. But wait ... if we detect the web framework type, we can say "hey, we think this should be the public folder and you are using Svelte" and prompt them with that. And give them the option to change it.

random thoughts

1. branch - in basic mode it should use the default branch, IMO.
2. name - we use a generated name based on the SWA URL (ex: snowy-trees)
3. api or functions should be the default (we look for those 2 only)
4. we dont ask for resource group nor location in basic mode

Microsoft Learn allows a learner to use an Azure sandbox. This is known as a concierge subscription.

This extension tries to create a resource group. But the sandbox has already created a resource group and does not allow the extension to create another one. So the user is presented with a dialog saying they dont have permission. But it does allow the user to select the existing resource group in the sandbox. (see the image below)

I propose that , ideally, the extension should detect if the subscription is a concierge/sandbox subscription that it should use the existing resource group, saving the learner from having to press the "select existing" button and then select it

cc @fiveisprime @craigshoemaker

Is your feature request related to a problem? Please describe. My issue is I do commit my .vscode/settings.json but I don't want to commit my peacock color customisation into it because each dev their own preference.

Describe the solution you'd like I think it would be nice if we have something like .vscode/peacock.json file config which I can add into my .gitignore settings.

Describe alternatives you've considered

Additional context

thanks for the feedback. please see #7 ... this is our issue for this topic and there is a dependency on a vs code feature. You can read the comments in that issue thread about several ideas and why a separate file wont work at this time.

• no peacock
• fix delete
• npm audit fix
• ng update angular
• ng up ngrx
• ng up rxjs
• npm up
• 7071 is for functions
• updating for func 1.2.2

• no peacock
• fix delete
• npm audit fix
• ng update angular
• ng up ngrx
• ng up rxjs
• npm up
• 7071 is for functions
• updating for func 1.2.2

• packages
• ng up
• ngrx store
• rxjs

updates for npm audit fixes

• packages
• ng up
• ngrx store
• rxjs

@craigshoemaker - i'm not sure how to re-word this. Based on what @miwebst says above, I get the issue ... but I wonder if this is something we can produce a better error message on. Or better yet, make the service handle it if its blank.

Otherwise ... we could word it as

This setting is optional except when you use a web framework that expects output to be placed in a distribution folder. In those cases, enter the distribution folder in this box.

I'm torn

Thanks. I'll take a look and see if I can get tests to work locally on yours. One thing that comes to mind is the the engine version ... I have had issues with that in the past.

Thank you @rohmanhm for creating this issue!

closes #397

closes #397

On the status bar I have a button for "Remote Host" which I noticed isn't flush with the top edge of the bar anymore. I thought there is an issue with the button's alignment, I did some digging and played around with workbench customizations, eventually I found #377. As a result even if the theme doesn't have a status bar border, it is added:

This is what it looked like before and what it looks like when I remove the Peacock's border setting from the workspace settings:

For reference here is a theme that does have a border (Peacock's colored border is still turned off):

Above the theme's own border doesn't stand out as much, since the border color is effectively coordinated with the theme color.

I read through the aforementioned issue, however, I fail to understand why it was an issue in the first place, because the author had overwritten the border colors in the user settings. Anyway, they probably had a good reason for this.

Of course there are many ways to get around this cosmetic issue, ideally there would be an option to not paint the status bar border nor the title bar one, (someone may eventually notice that MacOS dims the title bar, but not the border and that becomes another annoyance), however, I'd like to have a discussion about what would be an appropriate solution here first. Thanks.

im not sure the remote differentiates entirely. there is a property that gets set, but IIRC it isnt always accessible where I need peacock to read it.

If you have a repo which has dependabot enabled, it sometimes creates PRs.

The first PR will create the Preview URL. But for a SWA this is not desirable. It would be more valuable to be able to use it for my own PR. Otherwise, if I have 10 dependabot PRs, I have to hunt through which one caused the preview URL and close it. Closing it may not be desirable either.

I recommend we find a way to ignore the dependabot PRs.

Bumps prismjs from 1.20.0 to 1.21.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/PrismJS/prism/releases">prismjs's releases</a>.</em></p> <blockquote> <h2>v1.21.0</h2> <p>Release 1.21.0</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/PrismJS/prism/blob/master/CHANGELOG.md">prismjs's changelog</a>.</em></p> <blockquote> <h2>1.21.0 (2020-08-06)</h2> <h3>New components</h3> <ul> <li><strong>.ignore</strong> & <strong>.gitignore</strong> & <strong>.hgignore</strong> & <strong>.npmignore</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2481">#2481</a>) <a href="https://github.com/PrismJS/prism/commit/3fcce6fe"><code>3fcce6fe</code></a></li> <li><strong>Agda</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2430">#2430</a>) <a href="https://github.com/PrismJS/prism/commit/3a127c7d"><code>3a127c7d</code></a></li> <li><strong>AL</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2300">#2300</a>) <a href="https://github.com/PrismJS/prism/commit/de21eb64"><code>de21eb64</code></a></li> <li><strong>Cypher</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2459">#2459</a>) <a href="https://github.com/PrismJS/prism/commit/398e2943"><code>398e2943</code></a></li> <li><strong>Dhall</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2473">#2473</a>) <a href="https://github.com/PrismJS/prism/commit/649e51e5"><code>649e51e5</code></a></li> <li><strong>EditorConfig</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2471">#2471</a>) <a href="https://github.com/PrismJS/prism/commit/ed8fff91"><code>ed8fff91</code></a></li> <li><strong>HLSL</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2318">#2318</a>) <a href="https://github.com/PrismJS/prism/commit/87a5c7ae"><code>87a5c7ae</code></a></li> <li><strong>JS stack trace</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2418">#2418</a>) <a href="https://github.com/PrismJS/prism/commit/ae0327b3"><code>ae0327b3</code></a></li> <li><strong>PeopleCode</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2302">#2302</a>) <a href="https://github.com/PrismJS/prism/commit/bd4d8165"><code>bd4d8165</code></a></li> <li><strong>PureBasic</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2369">#2369</a>) <a href="https://github.com/PrismJS/prism/commit/d0c1c70d"><code>d0c1c70d</code></a></li> <li><strong>Racket</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2315">#2315</a>) <a href="https://github.com/PrismJS/prism/commit/053016ef"><code>053016ef</code></a></li> <li><strong>Smali</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2419">#2419</a>) <a href="https://github.com/PrismJS/prism/commit/22eb5cad"><code>22eb5cad</code></a></li> <li><strong>Structured Text (IEC 61131-3)</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2311">#2311</a>) <a href="https://github.com/PrismJS/prism/commit/8704cdfb"><code>8704cdfb</code></a></li> <li><strong>UnrealScript</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2305">#2305</a>) <a href="https://github.com/PrismJS/prism/commit/1093ceb3"><code>1093ceb3</code></a></li> <li><strong>WarpScript</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2307">#2307</a>) <a href="https://github.com/PrismJS/prism/commit/cde5b0fa"><code>cde5b0fa</code></a></li> <li><strong>XML doc (.net)</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2340">#2340</a>) <a href="https://github.com/PrismJS/prism/commit/caec5e30"><code>caec5e30</code></a></li> <li><strong>YANG</strong> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2467">#2467</a>) <a href="https://github.com/PrismJS/prism/commit/ed1df1e1"><code>ed1df1e1</code></a></li> </ul> <h3>Updated components</h3> <ul> <li>Markup & JSON: Added new aliases (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2390">#2390</a>) <a href="https://github.com/PrismJS/prism/commit/9782cfe6"><code>9782cfe6</code></a></li> <li>Fixed several cases of exponential backtracking (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2268">#2268</a>) <a href="https://github.com/PrismJS/prism/commit/7a554b5f"><code>7a554b5f</code></a></li> <li><strong>APL</strong> <ul> <li>Added <code>⍥</code> (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2409">#2409</a>) <a href="https://github.com/PrismJS/prism/commit/0255cb6a"><code>0255cb6a</code></a></li> </ul> </li> <li><strong>AutoHotkey</strong> <ul> <li>Added missing <code>format</code> built-in (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2450">#2450</a>) <a href="https://github.com/PrismJS/prism/commit/7c66cfc4"><code>7c66cfc4</code></a></li> <li>Improved comments and other improvements (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2412">#2412</a>) <a href="https://github.com/PrismJS/prism/commit/ddf3cc62"><code>ddf3cc62</code></a></li> <li>Added missing definitions (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2400">#2400</a>) <a href="https://github.com/PrismJS/prism/commit/4fe03676"><code>4fe03676</code></a></li> </ul> </li> <li><strong>Bash</strong> <ul> <li>Added <code>composer</code> command (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2298">#2298</a>) <a href="https://github.com/PrismJS/prism/commit/044dd271"><code>044dd271</code></a></li> </ul> </li> <li><strong>Batch</strong> <ul> <li>Fix escaped double quote (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2485">#2485</a>) <a href="https://github.com/PrismJS/prism/commit/f0f8210c"><code>f0f8210c</code></a></li> </ul> </li> <li><strong>C</strong> <ul> <li>Improved macros and expressions (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2440">#2440</a>) <a href="https://github.com/PrismJS/prism/commit/8a72fa6f"><code>8a72fa6f</code></a></li> <li>Improved macros (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2320">#2320</a>) <a href="https://github.com/PrismJS/prism/commit/fdcf7ed2"><code>fdcf7ed2</code></a></li> </ul> </li> <li><strong>C#</strong> <ul> <li>Improved pattern matching (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2411">#2411</a>) <a href="https://github.com/PrismJS/prism/commit/7f341fc1"><code>7f341fc1</code></a></li> <li>Fixed adjacent string interpolations (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2402">#2402</a>) <a href="https://github.com/PrismJS/prism/commit/2a2e79ed"><code>2a2e79ed</code></a></li> </ul> </li> <li><strong>C++</strong> <ul> <li>Added support for default comparison operator (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2426">#2426</a>) <a href="https://github.com/PrismJS/prism/commit/8e9d161c"><code>8e9d161c</code></a></li> <li>Improved class name detection (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2348">#2348</a>) <a href="https://github.com/PrismJS/prism/commit/e3fe9040"><code>e3fe9040</code></a></li> <li>Fixed <code>enum class</code> class names (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2342">#2342</a>) <a href="https://github.com/PrismJS/prism/commit/30b4e254"><code>30b4e254</code></a></li> </ul> </li> <li><strong>Content-Security-Policy</strong> <ul> <li>Fixed directives (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2461">#2461</a>) <a href="https://github.com/PrismJS/prism/commit/537a9e80"><code>537a9e80</code></a></li> </ul> </li> <li><strong>CSS</strong> <ul> <li>Improved url and added keywords (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2432">#2432</a>) <a href="https://github.com/PrismJS/prism/commit/964de5a1"><code>964de5a1</code></a></li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/PrismJS/prism/commit/187c8a607ee70c7914682870156faa31ed01f001"><code>187c8a6</code></a> 1.21.0</li> <li><a href="https://github.com/PrismJS/prism/commit/bf4f323391d546d4b2e1a388f05c512a27491e9c"><code>bf4f323</code></a> Changelog for v1.21.0 (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2507">#2507</a>)</li> <li><a href="https://github.com/PrismJS/prism/commit/8bba4880202ef6bd7a1e379fe9aebe69dd75f7be"><code>8bba488</code></a> Previewers: Fixed XSS (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2506">#2506</a>)</li> <li><a href="https://github.com/PrismJS/prism/commit/158caf52343e59a66c2351ff1d83648efe871e33"><code>158caf5</code></a> JSON: Greedy comments (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2479">#2479</a>)</li> <li><a href="https://github.com/PrismJS/prism/commit/f0f8210c1a9745c064d49bfb985544c654986b24"><code>f0f8210</code></a> Batch: Fix escaped double quote (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2485">#2485</a>)</li> <li><a href="https://github.com/PrismJS/prism/commit/649e51e56250a81dc0b0c4f5b3a4ea23e1c21834"><code>649e51e</code></a> Added support for Dhall (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2473">#2473</a>)</li> <li><a href="https://github.com/PrismJS/prism/commit/453079bf96746e0c44f90cb7cd90fcae9a5f94cc"><code>453079b</code></a> Line Numbers: Fixed class name on website</li> <li><a href="https://github.com/PrismJS/prism/commit/a0efa40bde420ac3923947be611ebe6b3f077dce"><code>a0efa40</code></a> Fixed Treeview page (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2484">#2484</a>)</li> <li><a href="https://github.com/PrismJS/prism/commit/78161d607fe7d493831ff19759aac951330134a1"><code>78161d6</code></a> VB: Added VBA alias (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2469">#2469</a>)</li> <li><a href="https://github.com/PrismJS/prism/commit/ed1df1e1208401a8b84330ecc39689fa37d0e9f6"><code>ed1df1e</code></a> Added support for YANG (<a href="https://github-redirect.dependabot.com/PrismJS/prism/issues/2467">#2467</a>)</li> <li>Additional commits viewable in <a href="https://github.com/PrismJS/prism/compare/v1.20.0...v1.21.0">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps elliptic from 6.5.2 to 6.5.3. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/indutny/elliptic/commit/8647803dc3d90506aa03021737f7b061ba959ae1"><code>8647803</code></a> 6.5.3</li> <li><a href="https://github.com/indutny/elliptic/commit/856fe4d99fe7b6200556e6400b3bf585b1721bec"><code>856fe4d</code></a> signature: prevent malleability and overflows</li> <li>See full diff in <a href="https://github.com/indutny/elliptic/compare/v6.5.2...v6.5.3">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps lodash from 4.17.15 to 4.17.19. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lodash/lodash/releases">lodash's releases</a>.</em></p> <blockquote> <h2>4.17.16</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li><a href="https://github.com/lodash/lodash/commit/1144918f3578a84fcc4986da9b806e63a6175cbb"><code>1144918</code></a> Rebuild lodash and docs</li> <li><a href="https://github.com/lodash/lodash/commit/3a3b0fd339c2109563f7e8167dc95265ed82ef3e"><code>3a3b0fd</code></a> Bump to v4.17.16</li> <li><a href="https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12"><code>c84fe82</code></a> fix(zipObjectDeep): prototype pollution (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4759">#4759</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/e7b28ea6cb17b4ca021e7c9d66218c8c89782f32"><code>e7b28ea</code></a> Sanitize sourceURL so it cannot affect evaled code (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4518">#4518</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/0cec225778d4ac26c2bac95031ecc92a94f08bbb"><code>0cec225</code></a> Fix lodash.isEqual for circular references (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4320">#4320</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4515">#4515</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/94c3a8133cb4fcdb50db72b4fd14dd884b195cd5"><code>94c3a81</code></a> Document matches* shorthands for over* methods (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4510">#4510</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4514">#4514</a>)</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.19">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~mathias">mathias</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps websocket-extensions from 0.1.3 to 0.1.4. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/faye/websocket-extensions-node/blob/master/CHANGELOG.md">websocket-extensions's changelog</a>.</em></p> <blockquote> <h3>0.1.4 / 2020-06-02</h3> <ul> <li>Remove a ReDoS vulnerability in the header parser (CVE-2020-7662, reported by Robert McLaughlin)</li> <li>Change license from MIT to Apache 2.0</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/faye/websocket-extensions-node/commit/8efd0cd6e35faf9bb9cb08759be1e27082177d43"><code>8efd0cd</code></a> Bump version to 0.1.4</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/3dad4ad44a8c5f74d4f8f4efd3f9d6e0b5df3051"><code>3dad4ad</code></a> Remove ReDoS vulnerability in the Sec-WebSocket-Extensions header parser</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/4a76c75efb1c5d6a2f60550e9501757458d19533"><code>4a76c75</code></a> Add Node versions 13 and 14 on Travis</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/44a677a9c0631daed0b0f4a4b68c095b624183b8"><code>44a677a</code></a> Formatting change: {...} should have spaces inside the braces</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/f6c50aba0c20ff45b0f87cea33babec1217ec3f5"><code>f6c50ab</code></a> Let npm reformat package.json</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/2d211f3705d52d9efb4f01daf5a253adf828592e"><code>2d211f3</code></a> Change markdown formatting of docs.</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/0b620834cc1e1f2eace1d55ab17f71d90d88271d"><code>0b62083</code></a> Update Travis target versions.</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/729a4653073fa8dd020561113513bfa2e2119415"><code>729a465</code></a> Switch license to Apache 2.0.</li> <li>See full diff in <a href="https://github.com/faye/websocket-extensions-node/compare/0.1.3...0.1.4">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency @typescript-eslint/eslint-plugin was updated from 2.34.0 to 3.0.0.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

Publisher: jameshenry License: MIT

<details> <summary>Release Notes for v3.0.0</summary>

<p>This major release has been a long time coming! We've been saving up breaking changes for a while now, waiting for the ESLint v7 release which we knew would deprecate support for node version 8.</p> <p>Due to our weekly release cadence, this major release mostly contains breaking changes!</p> <h1>Breaking Changes</h1> <h2>Dropped support for Node version 8 (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="547614026" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1420" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1420/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1420">#1420</a>)</h2> <p>In line with ESLint v7 - we've also dropped explicit support for node version 8.<br> This version of node has been end of life since 2019-12-31.<br> We no longer test against the version, so we provide no guarantees about whether or not future versions of our tooling will work on it.</p> <h2>Dropped support for TypeScript 3.2 (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="615467409" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/2004" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2004/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/2004">#2004</a>)</h2> <p>Old TS versions cause us maintenance pain as we work on integrating tightly with the TypeScript APIs for performance and stability reasons.</p> <p>As such we've updated our required TS version range to require a minimum of <code>>=3.3.1</code>.</p> <p>Each version of TS brings bugfixes and features, but most importantly they bring performance improvements. TS 3.9 is releasing with a host of performance improvements that will improve both your build times, <em>and</em> your lint times - so you should endeavour to upgrade if you can. We cannot provide any guarantees around the performance of old TS versions.</p> <h2>Configs</h2> <p>We've updated all of our configs! We've added new rules, old rules, and removed some stylistic rules.</p> <p>Both of the <code>recommended</code> and <code>recommended-requiring-typechecking</code> sets now inherit from the <code>eslint-recommended</code> set. We noticed that the majority of the time, users were using the sets in tandem, so this just removes one line of config for everyone.</p> <p>Check out the linked issues for more information about added/removed rules:</p> <ul> <li><code>eslint-recommended</code> config (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="529549688" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1273" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1273/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1273">#1273</a>)</li> <li><code>recommended</code> config (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="547833379" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1423" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1423/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1423">#1423</a>)</li> <li><code>recommended-requiring-typechecking</code> (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="547833379" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1423" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1423/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1423">#1423</a>)</li> </ul> <h2>Rules Changes</h2> <ul> <li><code>ban-types</code> got a rework of its default ban list to provide some more sensible defaults and remove fixers that caused users issues. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="480254667" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/848" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/848/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/848">#848</a>)</li> <li><code>no-floating-promises</code> now has the <code>ignoreVoid</code> option set to true by default. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="615461830" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/2003" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2003/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/2003">#2003</a>)</li> <li><code>no-unnecessary-condition</code> <ul> <li>the <code>ignoreRHS</code> option has been removed. The rule will now only check the RHS when it matters (i.e. in boolean contexts). (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="515015689" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1163" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/1163/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/1163">#1163</a>)</li> <li>the <code>checkArrayPredicates</code> option has been removed. The rule will now always check array predicate functions. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="561866894" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1579" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/1579/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/1579">#1579</a>)</li> <li>the rule now will report if you do an equality check against <code>null</code>/<code>undefined</code> when the value is not nullable. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="574215918" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1659" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/1659/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/1659">#1659</a>)</li> </ul> </li> <li><code>prefer-nullish-coalescing</code> <ul> <li>the fixer has been converted to a suggestion fixer always - it was unsafe in most cases.</li> <li>removed option <code>forceSuggestionFixer</code>.</li> </ul> </li> <li><code>prefer-optional-chain</code> <ul> <li>the fixer has been converted to a suggestion fixer always - it was unsafe in a number of cases.</li> <li>removed option <code>suggestInsteadOfAutofix</code>.</li> </ul> </li> <li><code>restrict-template-expressions</code> <ul> <li>now has the <code>allowNumber</code> option set to true by default. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="615475168" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/2005" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2005/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/2005">#2005</a>)</li> <li><code>allowNullable</code> has been renamed to <code>allowNullish</code>. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="615514963" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/2006" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2006/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/2006">#2006</a>)</li> </ul> </li> <li><code>strict-boolean-expression</code> received a complete rework. The rule is now more configurable, with smarter defaults and more intuitive logic. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="554999040" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1515" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1515/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1515">#1515</a>)</li> </ul> <h2>Rule Removals</h2> <p>The following deprecated rules have been deleted. Please switch to the listed alternative:</p> <ul> <li><code>ban-ts-ignore</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/ban-ts-comment.md"><code>ban-ts-comment</code></a></li> <li><code>camelcase</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/naming-convention.md"><code>naming-convention</code></a></li> <li><code>class-name-casing</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/naming-convention.md"><code>naming-convention</code></a></li> <li><code>generic-type-naming</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/naming-convention.md"><code>naming-convention</code></a></li> <li><code>interface-name-prefix</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/naming-convention.md"><code>naming-convention</code></a></li> <li><code>member-naming</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/naming-convention.md"><code>naming-convention</code></a></li> <li><code>no-untyped-public-signatures</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/explicit-module-boundary-types.md"><code>explicit-module-boundary-types</code></a></li> </ul> <h2>AST Changes</h2> <ul> <li><code>typescript-estree</code> now emits a <code>TSEmptyBodyFunctionExpression</code> when it encounters a function expression without a body. Previously this was done in <code>parser</code> (for legacy reasons). This change should only affect users directly consuming <code>typescript-estree</code>. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="530636231" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1289" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/1289/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/1289">#1289</a>)</li> <li>When a method is marked as optional (<code>class Foo { name?() {} }</code>) we now mark the <code>MethodDefinition</code>/<code>TSAbstractMethodDefinition</code> as optional. Previously we marked the <code>key</code> of the node as <code>optional</code>, but this only works if the <code>key</code> is an <code>Identifier</code>, and didn't work in the case of a computed <code>key</code> (<code>class Foo { ['name']?() {} }</code>). (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="548462110" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1429" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/1429/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/1429">#1429</a>)</li> <li>Import expressions (<code>import('foo')</code>) now conform to the newly released ESTree spec, outputting as an <code>ImportExpression</code>. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="608684416" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1950" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1950/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1950">#1950</a>)</li> <li>BigInt literals now conform to the newly released ESTree spec, outputting as a <code>Literal</code> with a value of type <code>bigint</code>. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="615430268" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1999" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1999/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1999">#1999</a>)</li> </ul> <h2>Parser Services</h2> <p><code>parserServices</code> are now always emitted from both <code>typescript-estree</code> and <code>parser</code>, regardless of the <code>parserOptions.project</code> configuration. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="469509028" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/716" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/716/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/716">#716</a>)</p> <p>This will allow you to consume parts of the TypeScript API that are generated at the file level, like variable usage diagnostics, without requiring full type information is generated for the project.</p> <p>Part of this change includes a new boolean flag on the output: <code>parserServices.hasFullTypeInformation</code> which is <code>true</code> when <code>parserOptions.project</code> was configured, and <code>false</code> otherwise.</p> <p>If you were using our <code>getParserServices</code> function from <code>experimental-utils</code>, then this will be handled automatically, and you will not notice any changes. If you built your own function for resolving the <code>parserServices</code>, then you'll have to update accordingly.</p> <h2>ESLint Types (experimental-utils)</h2> <p>The old version of our ESLint types were based on those found in the DefinitelyTyped repo. There was a lot of missing documentation, missing properties, misnamed types.</p> <p>As part of this release, we've reworked some of the internals to be much closer to the ESLint library itself. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="618016683" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/2023" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2023/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/2023">#2023</a>)</p> <p>As part of this change, we have also added the types for the new <code>ESLint</code> class.<br> <code>SourceCode.isSpaceBetween</code> has also been marked as optional, because it is only available in ESLint v6+</p> <h1>Non-breaking changes</h1> <h2>ESLint v7</h2> <p>We now have full support for ESLint v7 (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="557678953" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1550" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1550/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1550">#1550</a>).</p> <h2>Better handling for TS 3.9's non-null assertion changes (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="619839415" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/2036" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2036/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/2036">#2036</a>)</h2> <p><a href="https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-9.html#parsing-differences-in-optional-chaining-and-non-null-assertions" rel="nofollow">TS 3.9 introduced a breaking change for how non-null assertions are handled in optional chains</a>.</p> <p>Pre-3.9, <code>x?.y!.z</code> means <code>(x?.y).z</code> - i.e. it essentially scrubbed the optionality from the chain<br> Post-3.9, <code>x?.y!.z</code> means <code>x?.y!.z</code> - i.e. it just asserts that the property <code>y</code> is non-null, not the result of <code>x?.y</code></p> <p>Previously <code>x?.y!.z</code> produced <code>MemberExpression > TSNonNullAssertion > OptionalMemberExpression</code>.<br> Now it produces <code>OptionalMemberExpression > TSNonNullAssertion > OptionalMemberExpression</code>.</p> <p>Note that both <code>(x?.y)!.z</code> and <code>(x?.y!).z</code> still produce <code>MemberExpression > TSNonNullAssertion > OptionalMemberExpression</code>.<br> The same applies for call expressions.</p> <p>The rule <code>no-non-null-asserted-optional-chain</code> was also updated to handle this appropriately. It will no longer error on <code>x?.y!.z</code>, but it will still error on <code>(x?.y)!.z</code>.</p> <h2>Bug Fixes</h2> <ul> <li><strong>eslint-plugin:</strong> [dot-notation] fix typo in schema (<a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/2040" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2040/hovercard">#2040</a>) (<a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/242328fa749ee4c72af93433a9bef95f329ac62f">242328f</a>)</li> </ul> </details>

<details> <summary>Commits</summary> <p>The new version differs by 34 commits.</p> <ul> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/1765a178e456b152bd48192eb5db7e8541e2adf2"><code>1765a17</code></a> <code>chore: remove v3 canary Ci step</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/7e39f5ba32010a4853b11aa6e3af6985c6c6c25e"><code>7e39f5b</code></a> <code>v3.0.0</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/3dfc46dccbbd28eed2d74c7b6cacddf1a0848598"><code>3dfc46d</code></a> <code>feat: add index files to parser and typescript-estree</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/52b60852d0ba6bb6abe519c9d3ec1b231793e91d"><code>52b6085</code></a> <code>feat(eslint-plugin): [prefer-nullish-coalescing][prefer-optional-chain] remove unsafe fixers</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/ae82ea4a85a4ca332ebe6104e96c59dba30411be"><code>ae82ea4</code></a> <code>fix(experimental-utils): add back SourceCode.isSpaceBetweenTokens</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/fe59f69381a0915a4f5135e2e88637a5eea246ba"><code>fe59f69</code></a> <code>fix(eslint-plugin): correct parser peerDep version</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/f199cbdbbd892b5ba03bfff66f463f3d9c92ee9b"><code>f199cbd</code></a> <code>fix(typescript-estree): remove now defunct <code>Import</code> node type</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/a35026de2548d33963bbdb96fb8fffc7ab0d8a30"><code>a35026d</code></a> <code>chore: provide more granularity in the CI logs (#2024)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/06869c9656fa37936126666845aee40aad546ebd"><code>06869c9</code></a> <code>feat(experimental-utils): upgrade eslint types for v7 (#2023)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/208de71059746bf38e94bd460346ffb2698a3e12"><code>208de71</code></a> <code>feat: upgrade to ESLint v7 (#2022)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/7ad4d7c2db088b6f779b9d883a4acad13eee3775"><code>7ad4d7c</code></a> <code>feat: bump minimum required TS version (#2004)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/264b017c11c2ab132fcbad18b42a9a0fe639386e"><code>264b017</code></a> <code>feat(eslint-plugin): [restrict-template-expressions] rename <code>allowNullable</code> to <code>allowNullish</code> (#2006)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/bfd9b606d17d30d5694967a1f01e0e1501ba1022"><code>bfd9b60</code></a> <code>feat(eslint-plugin): [no-unnecessary-condition] remove <code>checkArrayPredicates</code> and always check it (#1579)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/7fa906073903c5eb70609c25f1a91ada14dcdc71"><code>7fa9060</code></a> <code>feat(eslint-plugin): [no-unnecessary-condition] report when non-nullish is compared to <code>null</code>/<code>undefined</code> (#1659)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/643ec240bd901295d9e9ea5c43fc20109c33e982"><code>643ec24</code></a> <code>feat(eslint-plugin): [restrict-template-expressions] <code>allowNumber: true</code> by default (#2005)</code></li> </ul> <p>There are 34 commits in total.</p> <p>See the <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/compare/f18890166146d8c6b8804ef705c04b15da269926...1765a178e456b152bd48192eb5db7e8541e2adf2">full diff</a></p> </details>

<details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>

Your Greenkeeper bot :palm_tree:

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency @typescript-eslint/parser was updated from 2.34.0 to 3.0.0.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

Publisher: jameshenry License: BSD-2-Clause

<details> <summary>Release Notes for v3.0.0</summary>

<p>This major release has been a long time coming! We've been saving up breaking changes for a while now, waiting for the ESLint v7 release which we knew would deprecate support for node version 8.</p> <p>Due to our weekly release cadence, this major release mostly contains breaking changes!</p> <h1>Breaking Changes</h1> <h2>Dropped support for Node version 8 (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="547614026" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1420" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1420/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1420">#1420</a>)</h2> <p>In line with ESLint v7 - we've also dropped explicit support for node version 8.<br> This version of node has been end of life since 2019-12-31.<br> We no longer test against the version, so we provide no guarantees about whether or not future versions of our tooling will work on it.</p> <h2>Dropped support for TypeScript 3.2 (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="615467409" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/2004" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2004/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/2004">#2004</a>)</h2> <p>Old TS versions cause us maintenance pain as we work on integrating tightly with the TypeScript APIs for performance and stability reasons.</p> <p>As such we've updated our required TS version range to require a minimum of <code>>=3.3.1</code>.</p> <p>Each version of TS brings bugfixes and features, but most importantly they bring performance improvements. TS 3.9 is releasing with a host of performance improvements that will improve both your build times, <em>and</em> your lint times - so you should endeavour to upgrade if you can. We cannot provide any guarantees around the performance of old TS versions.</p> <h2>Configs</h2> <p>We've updated all of our configs! We've added new rules, old rules, and removed some stylistic rules.</p> <p>Both of the <code>recommended</code> and <code>recommended-requiring-typechecking</code> sets now inherit from the <code>eslint-recommended</code> set. We noticed that the majority of the time, users were using the sets in tandem, so this just removes one line of config for everyone.</p> <p>Check out the linked issues for more information about added/removed rules:</p> <ul> <li><code>eslint-recommended</code> config (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="529549688" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1273" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1273/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1273">#1273</a>)</li> <li><code>recommended</code> config (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="547833379" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1423" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1423/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1423">#1423</a>)</li> <li><code>recommended-requiring-typechecking</code> (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="547833379" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1423" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1423/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1423">#1423</a>)</li> </ul> <h2>Rules Changes</h2> <ul> <li><code>ban-types</code> got a rework of its default ban list to provide some more sensible defaults and remove fixers that caused users issues. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="480254667" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/848" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/848/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/848">#848</a>)</li> <li><code>no-floating-promises</code> now has the <code>ignoreVoid</code> option set to true by default. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="615461830" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/2003" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2003/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/2003">#2003</a>)</li> <li><code>no-unnecessary-condition</code> <ul> <li>the <code>ignoreRHS</code> option has been removed. The rule will now only check the RHS when it matters (i.e. in boolean contexts). (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="515015689" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1163" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/1163/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/1163">#1163</a>)</li> <li>the <code>checkArrayPredicates</code> option has been removed. The rule will now always check array predicate functions. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="561866894" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1579" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/1579/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/1579">#1579</a>)</li> <li>the rule now will report if you do an equality check against <code>null</code>/<code>undefined</code> when the value is not nullable. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="574215918" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1659" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/1659/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/1659">#1659</a>)</li> </ul> </li> <li><code>prefer-nullish-coalescing</code> <ul> <li>the fixer has been converted to a suggestion fixer always - it was unsafe in most cases.</li> <li>removed option <code>forceSuggestionFixer</code>.</li> </ul> </li> <li><code>prefer-optional-chain</code> <ul> <li>the fixer has been converted to a suggestion fixer always - it was unsafe in a number of cases.</li> <li>removed option <code>suggestInsteadOfAutofix</code>.</li> </ul> </li> <li><code>restrict-template-expressions</code> <ul> <li>now has the <code>allowNumber</code> option set to true by default. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="615475168" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/2005" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2005/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/2005">#2005</a>)</li> <li><code>allowNullable</code> has been renamed to <code>allowNullish</code>. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="615514963" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/2006" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2006/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/2006">#2006</a>)</li> </ul> </li> <li><code>strict-boolean-expression</code> received a complete rework. The rule is now more configurable, with smarter defaults and more intuitive logic. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="554999040" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1515" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1515/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1515">#1515</a>)</li> </ul> <h2>Rule Removals</h2> <p>The following deprecated rules have been deleted. Please switch to the listed alternative:</p> <ul> <li><code>ban-ts-ignore</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/ban-ts-comment.md"><code>ban-ts-comment</code></a></li> <li><code>camelcase</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/naming-convention.md"><code>naming-convention</code></a></li> <li><code>class-name-casing</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/naming-convention.md"><code>naming-convention</code></a></li> <li><code>generic-type-naming</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/naming-convention.md"><code>naming-convention</code></a></li> <li><code>interface-name-prefix</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/naming-convention.md"><code>naming-convention</code></a></li> <li><code>member-naming</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/naming-convention.md"><code>naming-convention</code></a></li> <li><code>no-untyped-public-signatures</code> - replaced by <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/explicit-module-boundary-types.md"><code>explicit-module-boundary-types</code></a></li> </ul> <h2>AST Changes</h2> <ul> <li><code>typescript-estree</code> now emits a <code>TSEmptyBodyFunctionExpression</code> when it encounters a function expression without a body. Previously this was done in <code>parser</code> (for legacy reasons). This change should only affect users directly consuming <code>typescript-estree</code>. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="530636231" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1289" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/1289/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/1289">#1289</a>)</li> <li>When a method is marked as optional (<code>class Foo { name?() {} }</code>) we now mark the <code>MethodDefinition</code>/<code>TSAbstractMethodDefinition</code> as optional. Previously we marked the <code>key</code> of the node as <code>optional</code>, but this only works if the <code>key</code> is an <code>Identifier</code>, and didn't work in the case of a computed <code>key</code> (<code>class Foo { ['name']?() {} }</code>). (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="548462110" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1429" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/1429/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/1429">#1429</a>)</li> <li>Import expressions (<code>import('foo')</code>) now conform to the newly released ESTree spec, outputting as an <code>ImportExpression</code>. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="608684416" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1950" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1950/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1950">#1950</a>)</li> <li>BigInt literals now conform to the newly released ESTree spec, outputting as a <code>Literal</code> with a value of type <code>bigint</code>. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="615430268" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1999" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1999/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1999">#1999</a>)</li> </ul> <h2>Parser Services</h2> <p><code>parserServices</code> are now always emitted from both <code>typescript-estree</code> and <code>parser</code>, regardless of the <code>parserOptions.project</code> configuration. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="469509028" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/716" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/716/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/716">#716</a>)</p> <p>This will allow you to consume parts of the TypeScript API that are generated at the file level, like variable usage diagnostics, without requiring full type information is generated for the project.</p> <p>Part of this change includes a new boolean flag on the output: <code>parserServices.hasFullTypeInformation</code> which is <code>true</code> when <code>parserOptions.project</code> was configured, and <code>false</code> otherwise.</p> <p>If you were using our <code>getParserServices</code> function from <code>experimental-utils</code>, then this will be handled automatically, and you will not notice any changes. If you built your own function for resolving the <code>parserServices</code>, then you'll have to update accordingly.</p> <h2>ESLint Types (experimental-utils)</h2> <p>The old version of our ESLint types were based on those found in the DefinitelyTyped repo. There was a lot of missing documentation, missing properties, misnamed types.</p> <p>As part of this release, we've reworked some of the internals to be much closer to the ESLint library itself. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="618016683" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/2023" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2023/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/2023">#2023</a>)</p> <p>As part of this change, we have also added the types for the new <code>ESLint</code> class.<br> <code>SourceCode.isSpaceBetween</code> has also been marked as optional, because it is only available in ESLint v6+</p> <h1>Non-breaking changes</h1> <h2>ESLint v7</h2> <p>We now have full support for ESLint v7 (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="557678953" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/1550" data-hovercard-type="issue" data-hovercard-url="/typescript-eslint/typescript-eslint/issues/1550/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/1550">#1550</a>).</p> <h2>Better handling for TS 3.9's non-null assertion changes (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="619839415" data-permission-text="Title is private" data-url="https://github.com/typescript-eslint/typescript-eslint/issues/2036" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2036/hovercard" href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/pull/2036">#2036</a>)</h2> <p><a href="https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-9.html#parsing-differences-in-optional-chaining-and-non-null-assertions" rel="nofollow">TS 3.9 introduced a breaking change for how non-null assertions are handled in optional chains</a>.</p> <p>Pre-3.9, <code>x?.y!.z</code> means <code>(x?.y).z</code> - i.e. it essentially scrubbed the optionality from the chain<br> Post-3.9, <code>x?.y!.z</code> means <code>x?.y!.z</code> - i.e. it just asserts that the property <code>y</code> is non-null, not the result of <code>x?.y</code></p> <p>Previously <code>x?.y!.z</code> produced <code>MemberExpression > TSNonNullAssertion > OptionalMemberExpression</code>.<br> Now it produces <code>OptionalMemberExpression > TSNonNullAssertion > OptionalMemberExpression</code>.</p> <p>Note that both <code>(x?.y)!.z</code> and <code>(x?.y!).z</code> still produce <code>MemberExpression > TSNonNullAssertion > OptionalMemberExpression</code>.<br> The same applies for call expressions.</p> <p>The rule <code>no-non-null-asserted-optional-chain</code> was also updated to handle this appropriately. It will no longer error on <code>x?.y!.z</code>, but it will still error on <code>(x?.y)!.z</code>.</p> <h2>Bug Fixes</h2> <ul> <li><strong>eslint-plugin:</strong> [dot-notation] fix typo in schema (<a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/issues/2040" data-hovercard-type="pull_request" data-hovercard-url="/typescript-eslint/typescript-eslint/pull/2040/hovercard">#2040</a>) (<a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/242328fa749ee4c72af93433a9bef95f329ac62f">242328f</a>)</li> </ul> </details>

<details> <summary>Commits</summary> <p>The new version differs by 34 commits.</p> <ul> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/1765a178e456b152bd48192eb5db7e8541e2adf2"><code>1765a17</code></a> <code>chore: remove v3 canary Ci step</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/7e39f5ba32010a4853b11aa6e3af6985c6c6c25e"><code>7e39f5b</code></a> <code>v3.0.0</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/3dfc46dccbbd28eed2d74c7b6cacddf1a0848598"><code>3dfc46d</code></a> <code>feat: add index files to parser and typescript-estree</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/52b60852d0ba6bb6abe519c9d3ec1b231793e91d"><code>52b6085</code></a> <code>feat(eslint-plugin): [prefer-nullish-coalescing][prefer-optional-chain] remove unsafe fixers</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/ae82ea4a85a4ca332ebe6104e96c59dba30411be"><code>ae82ea4</code></a> <code>fix(experimental-utils): add back SourceCode.isSpaceBetweenTokens</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/fe59f69381a0915a4f5135e2e88637a5eea246ba"><code>fe59f69</code></a> <code>fix(eslint-plugin): correct parser peerDep version</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/f199cbdbbd892b5ba03bfff66f463f3d9c92ee9b"><code>f199cbd</code></a> <code>fix(typescript-estree): remove now defunct <code>Import</code> node type</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/a35026de2548d33963bbdb96fb8fffc7ab0d8a30"><code>a35026d</code></a> <code>chore: provide more granularity in the CI logs (#2024)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/06869c9656fa37936126666845aee40aad546ebd"><code>06869c9</code></a> <code>feat(experimental-utils): upgrade eslint types for v7 (#2023)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/208de71059746bf38e94bd460346ffb2698a3e12"><code>208de71</code></a> <code>feat: upgrade to ESLint v7 (#2022)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/7ad4d7c2db088b6f779b9d883a4acad13eee3775"><code>7ad4d7c</code></a> <code>feat: bump minimum required TS version (#2004)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/264b017c11c2ab132fcbad18b42a9a0fe639386e"><code>264b017</code></a> <code>feat(eslint-plugin): [restrict-template-expressions] rename <code>allowNullable</code> to <code>allowNullish</code> (#2006)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/bfd9b606d17d30d5694967a1f01e0e1501ba1022"><code>bfd9b60</code></a> <code>feat(eslint-plugin): [no-unnecessary-condition] remove <code>checkArrayPredicates</code> and always check it (#1579)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/7fa906073903c5eb70609c25f1a91ada14dcdc71"><code>7fa9060</code></a> <code>feat(eslint-plugin): [no-unnecessary-condition] report when non-nullish is compared to <code>null</code>/<code>undefined</code> (#1659)</code></li> <li><a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/commit/643ec240bd901295d9e9ea5c43fc20109c33e982"><code>643ec24</code></a> <code>feat(eslint-plugin): [restrict-template-expressions] <code>allowNumber: true</code> by default (#2005)</code></li> </ul> <p>There are 34 commits in total.</p> <p>See the <a href="https://urls.greenkeeper.io/typescript-eslint/typescript-eslint/compare/f18890166146d8c6b8804ef705c04b15da269926...1765a178e456b152bd48192eb5db7e8541e2adf2">full diff</a></p> </details>

<details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>

Your Greenkeeper bot :palm_tree:

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency @types/sinon was updated from 7.5.2 to 9.0.1.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

Publisher: types License: MIT

Find out more about this release.

<details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>

Your Greenkeeper bot :palm_tree:

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency istanbul-lib-instrument was updated from 3.3.0 to 4.0.3.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

Publisher: coreyfarrell License: BSD-3-Clause

Find out more about this release.

<details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>

Your Greenkeeper bot :palm_tree:

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency @types/node was updated from 12.12.16 to 13.13.3.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

Publisher: types License: MIT

Find out more about this release.

<details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>

Your Greenkeeper bot :palm_tree:

closes #397

I added new property Affect Status and Title Borders, which defaults to false. When false, the borders will not be colored for title nor status. When true, the borders will be colored only if the title or status are also colored , respectively.

v3.8.0 will have this change.

Peacock only works in workspaces because VSCode uses the settings.json file in the.vscode folder. I'm guessing this is why yours is not remembered.

if not, please provide more details.

Versions (please complete the following information):

• OS: Windows
• VS Code version 1.46.1
• Peacock Version 3.7.2

Describe the bug If it is opened into a folder on remote, the colors will not change, even though they might be set previously. In the docs it is noted that Peacock only works in a workspace, but it also works outside of a workspace. You can set colors and they are saved in settings.json. However the colors are not set when you access the remote target again, although you can trigger the colors by using Peacock's Peacock: Enter a color command once and then the settings.json file is read and the colors are updated as per normal.

To Reproduce Steps to reproduce the behavior:

1. Access remote workspace that doesn't have a .code-workspace extension, ie only settings.json in the .vscode folder
2. If you set colors using Peacock's Peacock: Enter a color command, the color will be set in settings.json and the colors will change. However if you exit and access the remote target again the colors will not be set even though the settings.json file is created.

Expected behavior

1. Expected that the colors set by Peacock will be saved and displayed on each session.

Screenshots If applicable, add screenshots to help explain your problem.

Additional context

1. This can be solved by creating a .code-workspace file instead of a settings.json file and accessing that remote workspace instead of accessing the root folder in the remote target.
2. The text in the settings.json folder is greyed out when a .code-workspace file is used.
3. Perhaps the docs on the remote section can be updated to note this if it is expected behavior?
4. Related to #333, Peacock works without a workspace, but won't persist.

Peacock only works in workspaces. This is due to how the settings.json file in the .vscode folder only gets created and applied for workspaces.

These are already colored using the complementary color in Peacock. (example bellow). If you want something different, please can you clarify?

  "workbench.colorCustomizations": {
    "activityBar.activeBackground": "#65c89b",
    "activityBar.activeBorder": "#945bc4",
    "activityBar.background": "#65c89b",
    "activityBar.foreground": "#15202b",
    "activityBar.inactiveForeground": "#15202b99",
    "activityBarBadge.background": "#945bc4",
    "activityBarBadge.foreground": "#e7e7e7",
    "editorGroup.border": "#65c89b",
    "panel.border": "#65c89b",
    "sideBar.border": "#65c89b",
    "statusBar.background": "#42b883",
    "statusBar.border": "#42b883",
    "statusBar.foreground": "#15202b",
    "statusBarItem.hoverBackground": "#359268",
    "titleBar.activeBackground": "#42b883",
    "titleBar.activeForeground": "#15202b",
    "titleBar.border": "#42b883",
    "titleBar.inactiveBackground": "#42b88399",
    "titleBar.inactiveForeground": "#15202b99",
    
  },
  "peacock.color": "#42b883"
}

@musicfuel - have you had a chance to play with this? I like that idea too

Bumps websocket-extensions from 0.1.3 to 0.1.4. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/faye/websocket-extensions-node/blob/master/CHANGELOG.md">websocket-extensions's changelog</a>.</em></p> <blockquote> <h3>0.1.4 / 2020-06-02</h3> <ul> <li>Remove a ReDoS vulnerability in the header parser (CVE-2020-7662, reported by Robert McLaughlin)</li> <li>Change license from MIT to Apache 2.0</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/faye/websocket-extensions-node/commit/8efd0cd6e35faf9bb9cb08759be1e27082177d43"><code>8efd0cd</code></a> Bump version to 0.1.4</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/3dad4ad44a8c5f74d4f8f4efd3f9d6e0b5df3051"><code>3dad4ad</code></a> Remove ReDoS vulnerability in the Sec-WebSocket-Extensions header parser</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/4a76c75efb1c5d6a2f60550e9501757458d19533"><code>4a76c75</code></a> Add Node versions 13 and 14 on Travis</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/44a677a9c0631daed0b0f4a4b68c095b624183b8"><code>44a677a</code></a> Formatting change: {...} should have spaces inside the braces</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/f6c50aba0c20ff45b0f87cea33babec1217ec3f5"><code>f6c50ab</code></a> Let npm reformat package.json</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/2d211f3705d52d9efb4f01daf5a253adf828592e"><code>2d211f3</code></a> Change markdown formatting of docs.</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/0b620834cc1e1f2eace1d55ab17f71d90d88271d"><code>0b62083</code></a> Update Travis target versions.</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/729a4653073fa8dd020561113513bfa2e2119415"><code>729a465</code></a> Switch license to Apache 2.0.</li> <li>See full diff in <a href="https://github.com/faye/websocket-extensions-node/compare/0.1.3...0.1.4">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps websocket-extensions from 0.1.3 to 0.1.4. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/faye/websocket-extensions-node/blob/master/CHANGELOG.md">websocket-extensions's changelog</a>.</em></p> <blockquote> <h3>0.1.4 / 2020-06-02</h3> <ul> <li>Remove a ReDoS vulnerability in the header parser (CVE-2020-7662, reported by Robert McLaughlin)</li> <li>Change license from MIT to Apache 2.0</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/faye/websocket-extensions-node/commit/8efd0cd6e35faf9bb9cb08759be1e27082177d43"><code>8efd0cd</code></a> Bump version to 0.1.4</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/3dad4ad44a8c5f74d4f8f4efd3f9d6e0b5df3051"><code>3dad4ad</code></a> Remove ReDoS vulnerability in the Sec-WebSocket-Extensions header parser</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/4a76c75efb1c5d6a2f60550e9501757458d19533"><code>4a76c75</code></a> Add Node versions 13 and 14 on Travis</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/44a677a9c0631daed0b0f4a4b68c095b624183b8"><code>44a677a</code></a> Formatting change: {...} should have spaces inside the braces</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/f6c50aba0c20ff45b0f87cea33babec1217ec3f5"><code>f6c50ab</code></a> Let npm reformat package.json</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/2d211f3705d52d9efb4f01daf5a253adf828592e"><code>2d211f3</code></a> Change markdown formatting of docs.</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/0b620834cc1e1f2eace1d55ab17f71d90d88271d"><code>0b62083</code></a> Update Travis target versions.</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/729a4653073fa8dd020561113513bfa2e2119415"><code>729a465</code></a> Switch license to Apache 2.0.</li> <li>See full diff in <a href="https://github.com/faye/websocket-extensions-node/compare/0.1.3...0.1.4">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps elliptic from 6.5.2 to 6.5.3. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/indutny/elliptic/commit/8647803dc3d90506aa03021737f7b061ba959ae1"><code>8647803</code></a> 6.5.3</li> <li><a href="https://github.com/indutny/elliptic/commit/856fe4d99fe7b6200556e6400b3bf585b1721bec"><code>856fe4d</code></a> signature: prevent malleability and overflows</li> <li>See full diff in <a href="https://github.com/indutny/elliptic/compare/v6.5.2...v6.5.3">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps elliptic from 6.5.2 to 6.5.3. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/indutny/elliptic/commit/8647803dc3d90506aa03021737f7b061ba959ae1"><code>8647803</code></a> 6.5.3</li> <li><a href="https://github.com/indutny/elliptic/commit/856fe4d99fe7b6200556e6400b3bf585b1721bec"><code>856fe4d</code></a> signature: prevent malleability and overflows</li> <li>See full diff in <a href="https://github.com/indutny/elliptic/compare/v6.5.2...v6.5.3">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>