Open zhaolinlau opened 1 year ago
I also have this issue. I hope the owner of this repository will come and take a look at this issue.
I believe you should be using ppm
instead of apm
for pulsar packages. Also this package hasn't been tested with pulsar. If someone wants to create a PR that changes the tests to use pulsar that would be much appreciated 😁👍. It is on my TODO list but it will take a while.
@UziTech I've been using this plugin with PulsarEdit for a few days and it seems okay so far.
@UziTech I've been using this plugin with PulsarEdit for a few days and it seems okay so far.
How did you install?
I cheated:
cp -r ~/.atom ~/.pulsar
cp -r ~/.config/Atom ~/.config/Pulsar
Also @zhaolinlau in Pulsar's Settings you should be able to install the package just like you would in Atom. The package is on the Pulsar Package Registry
Also @zhaolinlau in Pulsar's Settings you should be able to install the package just like you would in Atom. The package is on the Pulsar Package Registry
Same error
Also @zhaolinlau in Pulsar's Settings you should be able to install the package just like you would in Atom. The package is on the Pulsar Package Registry
Same error
So quick disclaimer I'm not affiliated with this codebase at all, but am a maintainer of Pulsar, that's why I suggested it.
But if you are in fact getting the exact same error as above in Pulsar, you have Visual Studio Code 2022 installed. Pulsar is still doing it's best to update our versions of Node, Electron, NPM and friends.
But what that does mean is they don't recognize such a new Visual Studio Code installation. For Pulsar we would recommend installing the 2019 version.
The reason Pulsar cares about Visual Studio is when you install some native packages they need to be built for each OS, and that's done with a C++ toolchain program installed, which Visual Studio is one.
And apparently this repo is a package that needs to be built on installation.
Description
Steps to reproduce
Expected behavior: Installing minimap to C:\Users\Win10.pulsar\packages done
Actual behavior: Installing x-terminal to C:\Users\Win10.pulsar\packages failed
Reproduces how often: 100%
Versions
OS name and version: Windows 11 22H2 Terminal version: PowerShell 7.3.1
Additional context