coc-extensions / coc-powershell

PowerShellEditorService integration for coc.vim

coc-powershell

A vim plugin powered by PowerShellEditorServices and coc.nvim to provide a rich PowerShell editing experience.

Features include:

• Intellisense/Completions
• Go to definition
• PSScriptAnalyzer integration
• Integrated REPL environment that shares the context with the language services
• and much more!

Prerequisites

1. Vim 8.0+ or NeoVim
2. PowerShell Core or Windows PowerShell
3. coc.nvim

Installation

coc-powershell is an extension for coc.nvim. You can install coc.nvim with a plugin manager like vim-plug:

Plug 'neoclide/coc.nvim', {'branch': 'release'}

Then, use :CocInstall coc-powershell to install.

Alternatively, you can have coc.nvim automatically install the extension if it's missing:

let g:coc_global_extensions=[ 'coc-powershell', ... ]

Configuration

Disable the integrated console

You can disable the integrated console when a PowerShell file is opened by editing your coc-settings.json file and setting powershell.integratedConsole.showOnStartup to false.

{
    "powershell.integratedConsole.showOnStartup": false
}

Recommended plugins

• coc-snippets Used to allow snippets (requires neovim 0.4 or latest vim8).
  • Can be installed with :CocInstall coc-snippets
• vim-polyglot for syntax highlighting 🎨

coc-powershell's Issues

.pses folders get created in my cwd and don't get cleaned up

We should probably move that somewhere else...

[coc.nvim] Error on active extension coc-powershell: TypeError: (intermediate value) is not iterable

System Details

• Vim or NeoVim?: Vim
• Version of Vim (run vim --version) or NeoVim (run nvim --version): 8.1
• Version of coc-powershell (in Vim or NeoVim: :CocList extensions coc-powershell): 0.0.21
• Operating System: Windows 10
• PowerShell version (in PowerShell: $PSVersionTable): 5.1.17763.592

Issue Description

[coc.nvim] Error on active extension coc-powershell: TypeError: (intermediate value) is not iterable

Expected Behaviour

No error on loading extension

Actual Behaviour

Above error
and extension not active.

CocInfo:

## versions

vim version: VIM - Vi IMproved 8.1 (2018 May 18, compiled May 18 2018 18:36:07)
node version: v10.16.3
coc.nvim version: 0.0.74-e04013a8bd
term: undefined
platform: win32

## Messages
Messages maintainer: Bram Moolenaar <[email protected]>
"\tmp\Powershell Scripts\Find-GPObyMatch.ps1" 0L, 0C
[coc.nvim] Error on active extension coc-powershell: TypeError: (intermediate value) is not iterable
## Output channel: snippets


## Output channel: powershell

starting.
pwshPath = C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
bundledModulesPath = C:\Users\ankarloog\Dropbox\Utilities\gVimPortable8\Data\settings\AppData\Local\coc\extensions\node_modules\coc-powershell\PowerShellEditorServices

Autoformat command

Is it possible to use this to autoformat powershell code ?

^M at the end of lines when formatting with coc-nvim

System Details

• Vim or NeoVim?:NeoVim
• Version of Vim (run vim --version) or NeoVim (run nvim --version):0.4.4
• Version of coc-powershell (in Vim or NeoVim: :CocList extensions coc-powershell):0.1.14
• Operating System:windows 10
• PowerShell version (in PowerShell: $PSVersionTable):7.1.1

Issue Description

I am experiencing a problem with...
formatting ps1 files

xmap <leader>f <Plug>(coc-format-selected) nmap <leader>f <Plug>(coc-format-selected)
formats the selected file but results in ^M at the end of every line.
I have a .editconfig file and tested it with opening and loading files with all 3 possible lineendings. Checked the line endings.
But no matter what I get the ^M after formatting

Expected Behaviour

Formatted without the ^M

-- Description of what should be happening --

Actual Behaviour

-- Description of what actually happens --

Completion suggestion - fuzzy search

Looks like by default auto-completion uses some fuzzy search and then sort results alphabetically. For example if I type Get-Dat, it wll list about 30 Get-AZDataLake* cmdlets first (Get-Date will be in the bottom). How to change it to use exact match (it works like that in VSCode)?

PSES Preview doesn't load

System Details

• Vim or NeoVim?: NeoVim

• Version of Vim (run vim --version) or NeoVim (run nvim --version): NVIM v0.4.0-1234-g1b99aa8c5 (a few days old nightly)

• Version of coc-powershell (in Vim or NeoVim: :CocList extensions coc-powershell): 0.0.17 (local build with attempts to add powershell/showHelp command)

• Operating System: Windows 10 build 18922 (insiders build)

• PowerShell version (in PowerShell: $PSVersionTable): 5.1.18922.1000

Issue Description

Using downloadPSES.ps1 with the -AllowPreRelease flag. Getting the message:

An error occurred while starting PowerShell Editor Services:

The argument is null. Provide a valid value for the argument, and then try running the command again.
   at System.Management.Automation.ValidateNotNullAttribute.Validate(Object arguments, EngineIntrinsics engineIntrinsics)
   at System.Management.Automation.ParameterBinderBase.BindParameter(CommandParameterInternal parameter, CompiledCommandParameter parameterMetadata, ParameterBindingFlags flags)

Expected Behaviour

Would expect PSIC to load without issue.

Actual Behaviour

Receiving error in attempting to load PSIC.

Consider renaming to vim-powershell?

Just because there's https://github.com/PowerShell/vscode-powershell and vim-powershell is actually the repo name we used for the original one that shipped in CloudShell.

Just a thought.

I'd also want to talk to https://github.com/ant-druha/powershell about calling it intellij-powershell 😃

We'd wanna get sign off from @corbob before the name change though - don't want to step on any toes but I think he's really interested in what you're doing in this repo 😄

Add recommended keybindings to README?

To help bootstrap those who want to use this 😃

powershell.integratedConsole.showOnStartup set to false issue

"Changing powershell.integratedConsole.showOnStartup to false disables entire functionality."

From #35

We should verify and figure out what to do. We may need to resort to Stdio in this case if we cant hide the terminal

Consider bundling PowerShell Editor Services with coc-powershell

All we need to do is include PSES as part of the files we want to go in the package.

Positives

• offline use - fixes #32
• instant first time start up
• No more confusion if the user doesn’t have airline that says it’s downloading pses.
• no more dependency on node-powershell

Negatives

• larger package size
• fixed to PSES version
• locked in to stable (or Preview?) version of PSES… or need to be clever

Here’s what this would look like in PR form

CocCommand powershell.execute spawns new terminal

System Details

• Vim or NeoVim?: Both
• _Version of Vim : VIM - Vi IMproved 8.0, NVIM v0.3.7
• _Version of coc-powershell : coc-powershell 0.0.18
• Operating System: Ubuntu 18.04
• _PowerShell version : 6.2.1

Issue Description

Running :CocCommand powershell.execute spawns new terminal on top of PowerShell Integrated Console and exits

Expected Behaviour

Code should run in existing terminal console

Actual Behaviour

Code runs in new terminal console on top of existing one.

powershell.evaluateLine and powershell.evaluateSelection runs as expected.

Would be good to be able to specify PSES version for install.ps1

With PSES currently split between "legacy" and "2.0.0" it would be good to be able to specify which one you want to install.

I have some ideas in my head where we use a variable to specify so the user can add it to their vimrc and get the prerelease version. I'll play around with it this weekend and open a PR if I can get it working the way I think it should.

Write tests... in TS!

naturally we should be testing our stuff somehow.

Error on Notification Coc-Rename -> "rename": rename provider not found for current buffer

System Details

• Vim or NeoVim?: NeoVim 0.5
  NVIM v0.5.0-dev+1118-gdf4440024
• _Version of coc-powershell 0.1.4
• Operating System: Windows
• PowerShell version (in PowerShell: $PSVersionTable): 7.1.3

Issue Description

We used to be able to rename functions and variables in powershell right? It is no longer working, using coc-rename
Error:
Error on Notificatioon "rename": rename provider not found for current buffer

Does coc-powershell provide rename functionality for functions and variables??

Can someone else please confirm?

Close shell window when last powershell script is closed

I often close my PS script using :q, but then the shell remains, and I have to close gvim manually to get rid of it.
Even worse, if I'm using vim from the command line, I can't exit it (typical vim problem I know) because there seems to be no way to close the shell (exit doesn't work).

So it would be handy if in this case, the shell would automatically close.

Unless there's some way to close the shell that I don't know about.

Can't get it to work on Ubuntu

I installed all prereqs and followed Install guide without any error. But still can't see Intellisense/Completion while editing ps1 file. Is there any additional parameters need to be added on vimrc?

option: preview version of PSES

downloadPSES.ps1 is failing to download PSES

System Details

• Version of coc-powershell (in Vim or NeoVim: :CocList extensions coc-powershell): git master branch
• Operating System:
• PowerShell version (in PowerShell: $PSVersionTable): 6.2.2 (and 5.1.something)

Issue Description

I am experiencing a problem with downloading PSES.

Expected Behaviour

Download PSES to the appropriate location.

Actual Behaviour

PowerShell 6.2.2:

Determining latest PowerShell Editor Services release...
Latest Release: v1.13.0
Downloading PowerShell Editor Services: v1.13.0
Invoke-WebRequest : 
NoSuchKeyThe specified key does not exist.36031537/f3b09080-dec1-11e9-8d4e-c1ba1fad71876C97CA7C937FCCA2RtSJjfM2979FzMEYkhxTRxkRkDBk4YZooVPjCpL2nAw1ZrtHL/I+zDuUhcNbMyfl5hCuZivIaks=
At /home/vsts/work/1/s/downloadPSES.ps1:29 char:1
+ Invoke-WebRequest $download -OutFile $zip
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (Method: GET, Reques\u2026PowerShell/6.2.3
}:HttpRequestMessage) [Invoke-WebRequest], HttpResponseException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
##[error]PowerShell exited with code '1'.

PowerShell 5.1:

Determining latest PowerShell Editor Services release...
Latest Release: v1.13.0
Downloading PowerShell Editor Services: v1.13.0
Invoke-WebRequest : The remote server returned an error: (404) Not Found.
At C:\code\coc-powershell\downloadPSES.ps1:29 char:1
+ Invoke-WebRequest $download -OutFile $zip
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

I'll take a look at what's going on, in particular why we're getting different errors between Windows PowerShell and PowerShell Core. If I were to guess, this started happening with the recent update to PSES, but I can't say for sure. I noticed the build failing in #74

Ability to unlist Terminal buffer so it doesn't show up in buffer list

EDIT FROM MAINTAINER:

Give me the ability to unlist the terminal buffer so it doesn't show up in buffer list.

ORIGINAL ASK:

Is there anyway to close the powershell integrated console in neovim? It keeps on launching, even if I kill the buffer it automatically recreates itself.

Build Enhancement

Summary of the new feature

I was looking at the build.ps1, and I noticed that we now have a few checks for folders (PSES and Snippets), but no way to "clean" the environment. Before working on a bunch of scripts for this, I thought I would put it out there to consider different options and decide upon one? My preference would be to consider Invoke-Build that is used by vscode-powershell, but that's only because I have experience with it. Are there other build methods that we could use?

Is it worthwhile to continue creating our own build scripts to reduce dependencies?

Console issues

This configuration doesn't seem to work:
"powershell.integratedConsole.focusConsoleOnExecute":true

If I close PSIC window and execute evaluateSelection or Execute commands PSIC window will not come back.

Other thing. I was browsing extensions.js file, I see that consoleTerminal has show and hide methods. Is it possible to map those as coc commands? (assuming these methods showing/hiding that terminal window indeed). This would let us to implement proper toggling feature (I opened a ticket with cocnvim but it probably will take a while/forever)

Add a prepackaged release for windows

Hey there! Id love to use this extension, however I'm dealing with difficulties compiling the typescript in my companies environment due to lack of internet access, I was wondering if you could provide a release tag with a pre built package. Any help would be appreciated!

add command: `powershell.evaluateSelection`

Add integrations?

Summary of the new feature

On the vscode-powershell repository there is integrations setup for Codacy and Dependabot. Would it be an idea to add those here as well? Dependabot at least would allow us to ensure we're keeping somewhat up to date on dependencies with hopefully less effort.

Add command: `powershell.testThis`, `powershell.testAll`

Commands documentation

Is there some sort of documentation explaining how to use this ? How to trigger REPL on/off, how to run current code in shell etc?

Looks like changing powershell.integratedConsole.showOnStartup to false disables entire functionality. Is there a way to disable command shell at the bottom but keep the autocomplete functionality ?

Bring back features from vimL version

@corbob added the preview feature which allowed you to get the preview version of PSES

I added the ability to switch between version of PS (PowerShell Core, Windows PowerShell).

We should bring these back now that we're in typescript

Linting (Diagnostics) doesn't work

System Details

• Vim or NeoVim?: both
• Version of Vim (run vim --version) or NeoVim (run nvim --version): Neovim 0.4.3
• _Version of coc-powershell : 0.1.1
• Operating System: linux
• PowerShell version (in PowerShell: $PSVersionTable): 7

Issue Description

I'm installing coc-extensions on the plain containers (various OS). Looks like there is some issue with linting for coc-powershell and coc-omnisharp. Initially I thought it's some global coc-nvim issue, because linting didn't work with python extension either. However after installing msft python server it was fixed. Then I realized linting is working with my old coc-powershell fork (I think it was v0.73).
When I do CocInfo using latest coc-powershell/omnisharp I see additional output channel (cs and ps1). Using my old fork I only see one output channel (Powershell or omnisharp)

Expected Behaviour

Actual Behaviour

-- Description of what actually happens --

Setting powerShellExePath crashes on extension load

System Details

• Vim or NeoVim?: NeoVim
• Version of Vim (run vim --version) or NeoVim (run nvim --version): v0.4.0-259-g9b4383261
• Version of coc-powershell (in Vim or NeoVim: :CocList extensions coc-powershell): 0.0.19
• Operating System: Windows 10 1903
• PowerShell version (in PowerShell: $PSVersionTable): 7.0.0-preview.2

Issue Description

Adding config option powershell.powerShellExePath in CocConfig causes extension to crash on load.

Expected Behaviour

The specified PowerShell executable is used.

Actual Behaviour

Receive error message on extension load:

[coc.nvim] Error on active extension coc-powershell: TypeError: Cannot read property 'powerShellExePath' of undefined

powershell.evaluateSelection - executes entire line, not a selection

In case if you select only some part of a single line, evaluateSelection will expand it to include entire row. For example if I only want to select and execute command in bold I'll get error:

if ( test-path ./somefile) {
....
}

Can we tweak it to run selection only?

Integrated PS console - follow up

Did some clean up/overview and realize some old issues are still there

1. Despite #52 powershell.execute command still doesn't work properly, file path is generated but is sent to a new terminal (not the integrated one) and closes immediately. Tested in both vim/nvim (latest) on a fresh Ubuntu container.

2. evaluateSelection doesn't work in Vim (works fine in NeoVim). Getting this error:
   request error nvim_buf_get_mark buf_get_mark support current buffer only

3. Integrated console doesn't work in Windows. gVim throws some error, but neovim just not loading it (using latest versions of both). I guess vim is not the best option for powershell stuff on windows anyway, so this is more like FYI, in case anybody is willing to research that.

How does one write tests in vimscript

Implement the client in typescript?

We don't go as far as the vscode extension - but we copy more-or-less the same settings and snippets to leverage those.

Thoughts?

Project license

My default opt-in is MIT license but I'd like to know what you guys think. :)

Should have a CONTRIBUTING.md file

Summary of the new feature

I spent an hour and a half on stream trying to get coc.nvim to load the local repository instead of pulling from npm. It would probably be a good idea to have a CONTRIBUTING.md file that can assist with a basic setup to allow local modifications of the file (the fun part for me was figuring out that I needed to run build.ps1 instead of the yarn install command recommended by coc.nvim.

I think taking a page from coc.nvim's file might be a good place to start, although it might also be overkill.

No handler registered for Request type 'powershell/getCommand'

I'm trying to mimic some of the things we do in vscode-powershell, to get my feet wet with how the Language Client works. I think I need to call CocRequestAsync (or not Async, but really, should be Async...). When I try the only thing I'm getting in the log is:

2019-04-17 22:22:26.612 [VERBOSE] tid:18 in 'ReadMessage' C:\PowerShellEditorServices\src\PowerShellEditorServices.Protocol\MessageProtocol\MessageReader.cs: line 138
    Received Request 'powershell/getCommand' with id 2

    {
      "jsonrpc": "2.0",
      "id": 2,
      "method": "powershell/getCommand",
      "params": "get-help"
    }

2019-04-17 22:22:26.612 [WARNING] tid:18 in 'DispatchMessage' C:\PowerShellEditorServices\src\PowerShellEditorServices.Protocol\MessageProtocol\MessageDispatcher.cs: line 134
    MessageDispatcher: No handler registered for Request type 'powershell/getCommand'

The steps to reproduce are:

" Either add this to init.vim/vimrc or otherwise create the function.
function! CallBack(a) abort
    echo a:a
endfunction

Call the Requestion function:
:call CocRequestAsync('pses', 'powershell/getCommand', 'get-help', function('CallBack'))

The 'powershell/getCommand' message sent to PSES when given a parameter should return information about the command.

Is this a case of needing to register the request type with coc.nvim or coc-pses?

feature: Restart terminal

Summary of the new feature

Wondering if we can port vscode's "Restart current session" to this extension. I did some research about a year ago, and the only way to do this was to kill terminal pid directly. But somehow it was messing up my colors (I had separate theme for terminal and files). Maybe this can be achieved via language server now

Another thing I was looking for is to get powershell console up even without opening ps files. More like an alternative for calling :term, I think it's psic is more robust. Probably this can be achieved by vim settings, but might be another option for ps extensions.

coc-powershell unresponsive

System Details

• Vim or NeoVim?: NeoVim
• Version of Vim (run vim --version) or NeoVim (run nvim --version): 0.4.3
• Version of coc-powershell (in Vim or NeoVim: :CocList extensions coc-powershell): 0.1.2
• Operating System: Windows 10 - 1909
• PowerShell version (in PowerShell: $PSVersionTable): 7.0.3

Issue Description

I am experiencing a problem with...

I run 'nvim some.ps1', the file opens, Neovim recognizes it as a Powershell file (according to statusline, but nothing else happens. There's no syntax highlighting, no linting, no completion, no terminal. If I manually start the extension, the integrated terminal appears, but the other features are still missing.

Expected Behaviour

-- Description of what should be happening --

I should open a ps1 file. the integrated terminal should open. I should see syntax highlighting, code completion, and linting.

Actual Behaviour

-- Description of what actually happens --

Nothing happens. It doesn't seem like the extension is functioning at all. Other extensions are functioning - the extensions for Rust and Python are functioning. I've also duplicated the same problem in vim 8.2, as well as with Neovim 0.4.4/pwsh 7.0.1/coc-powershell 0.1.2 on Ubuntu 18.04 WSL.

Adding Snippets

Another useful feature to have. I personally like ISE way (ctr + j), but VSCode is good too (just typing snippet name and it appears on the autocomplete list).

Expose a function to set the powershellExecutable used

Right now we use a global variable - but it might be more intuitive if we expose a function to set it... this function could also set it to a json file so that the value can be persisted.

switch between version of PS (PowerShell Core, Windows PowerShell).

We can have a command like powershell.setVersion.

few improvements

- powershell.Execute
use .'/path/to/file.ps1' instead of &'path/to/file'
Current version runs as job, so it's just printing standard output, and not loading variables to current session (say if I execute $a = 10; Write-Host $a I'll see output on the terminal, but variable $a won't be created)
Also, need some setting to skip Y/N prompt (and save file by default). Or a separate command like powershell.ExecuteForce.

- Readme
Move polyglot and coc-snippet to prereq section (first one is required to make it work). Also, snippet seemed to work with older versions of neovim (tried on 0.34), do we need a note about 0.4 version?

(not important) looking for some way to hide pwsh buffer from airline's tabline. Looks like its possible to hide all terminals (using let g:airline#extensions#tabline#ignore_bufadd_pat), wondering if there is a way to hide just integrated pwsh? Similar to how NERDTree is hidden.
Or other good option - open ps console prior the ps1 file, so console will be buffer 1 and file buffer 2 toggling console

Pester test codelens

add command: `powershell.executeFile`

This command should kick start a terminal and run powershell to execute the current script.

How to set different path to pwsh?

Trying to use pwsh-preview on linux in neovim but can't figure out how to set it. I tried to put the below setting in CocConfig, but getting error about undefined powerShellExePath:

{
"powershell.powerShellExePath":"/opt/microsoft/powershell/7-preview/pwsh" 
}

Any suggestion?

Error on active extension coc-powershell: TypeError: (intermediate value) is not iterable

This is a follow up on #34
I'm installing everything from scratch (on pwsh ubuntu container), then using this vimrc. After PlugInstall and CocInstall coc-powershell it start downloading PSES but soon after throwing this error:

[coc.nvim] Error on active extension coc-powershell: TypeError: (intermediate value) is not iterable

Here is CocInfo:

versions

~ |
~ | vim version: VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jun 06 2019 17:31:41)
~ | node version: v10.16.0
~ | coc.nvim version: 0.0.72-36b226e965
~ | term: dumb
~ | platform: linux
~ |
~ | ## Messages
~ | Messages maintainer: Bram Moolenaar [email protected]
~ | "test5.ps1" 0L, 0C
~ | [coc.nvim] Error on active extension coc-powershell: TypeError: (intermediate value) is not iterable
~ | ## Output channel: powershell
~ |
~ | starting.
~ | pwshPath = /usr/bin/pwsh
~ | bundledModulesPath = /root/.config/coc/extensions/node_modules/coc-powershell/PowerShellEditorServices

figure out how to communicate with PSES

Apart from stdio doing LSP, we should have a side channel for REPL functionalities.

add command: `powershell.searchOnlineHelp`

in a local scenario, this command should open a web url pointing to the online help.

Incorrect completion suggestions in Intergrated Terminal

I stumbled across this almost right away, after the most recent update, but haven't had a chance to submit a report, until now.

System Details

• Vim or NeoVim?:
  NeoVim
• Version of Vim (run vim --version) or NeoVim (run nvim --version):
  0.4.4
• Version of coc-powershell (in Vim or NeoVim: :CocList extensions coc-powershell):
  0.1.3
• Operating System:
  Win10 - 1909
• PowerShell version (in PowerShell: $PSVersionTable):
  7.0.3

Issue Description

I am experiencing a problem with...

When using the Integrated Console, if I enter a remote PSSession and try to use completion with any command (like cd or ls, etc), I only get suggestions from the local directory - not the remote one that I'm currently in.

Expected Behaviour

-- Description of what should be happening --

I should receive completion suggestions for the current remote session.

Actual Behaviour

-- Description of what actually happens --

I'm getting only suggestions from the last local directory I was in, before entering the remote PS Session.

can not install due to nodes problem

System Details

NeoVim_:NVIM v0.4.4

• Version of Vim (run vim --version) or NeoVim (run nvim --version):
• Version of coc-powershell (in Vim or NeoVim: :CocList extensions coc-powershell): can not install
  Operating System: windows 10
• PowerShell version (in PowerShell: $PSVersionTable): 7.1.0

Issue Description

can not install coc-powershell with
let g:coc_global_extensions=['coc-powershell']

Expected Behaviour

should install

Actual Behaviour

get this log file....

npm resolution error report

2021-01-07T22:09:00.571Z

Found: @types/[email protected]
node_modules/@types/node
dev @types/node@"~10.17.19" from the root project
@types/node@"*" from @types/[email protected]
node_modules/@types/follow-redirects
dev @types/follow-redirects@"^1.8.0" from the root project

Could not resolve dependency:
dev coc.nvim@"~0.0.77" from the root project

Conflicting peer dependency: @types/[email protected]
node_modules/@types/node
peer @types/node@"10.12.0" from [email protected]
node_modules/coc.nvim

Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

Raw JSON explanation object:

{
"code": "ERESOLVE",
"current": {
"name": "@types/node",
"version": "10.17.50",
"location": "node_modules/@types/node",
"dependents": [
{
"type": "dev",
"name": "@types/node",
"spec": "10.17.19",
"from": {
"location": "C:\Users\JMWINT1\AppData\Local\Temp\coc-powershell-Ivsm6i"
}
},
{
"type": "prod",
"name": "@types/node",
"spec": "*",
"from": {
"name": "@types/follow-redirects",
"version": "1.13.0",
"location": "node_modules/@types/follow-redirects",
"dependents": [
{
"type": "dev",
"name": "@types/follow-redirects",
"spec": "^1.8.0",
"from": {
"location": "C:\Users\JMWINT1\AppData\Local\Temp\coc-powershell-Ivsm6i"
}
}
]
}
}
]
},
"edge": {
"type": "dev",
"name": "coc.nvim",
"spec": "0.0.77",
"error": "MISSING",
"from": {
"location": "C:\Users\JMWINT1\AppData\Local\Temp\coc-powershell-Ivsm6i"
}
},
"peerConflict": {
"name": "@types/node",
"version": "10.12.0",
"whileInstalling": {
"name": "coc-powershell",
"version": "0.1.4",
"path": "C:\Users\JMWINT1\AppData\Local\Temp\coc-powershell-Ivsm6i"
},
"location": "node_modules/@types/node",
"dependents": [
{
"type": "peer",
"name": "@types/node",
"spec": "10.12.0",
"from": {
"name": "coc.nvim",
"version": "0.0.80",
"whileInstalling": {
"name": "coc-powershell",
"version": "0.1.4",
"path": "C:\Users\JMWINT~1\AppData\Local\Temp\coc-powershell-Ivsm6i"
},
"location": "node_modules/coc.nvim",
"dependents": []
}
}
]
},
"strictPeerDeps": false,
"force": false
}