Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spicetify-cli: Some scripts are not recognised as cmdlet, scripts, ... #66

Open
jacob-thanh opened this issue Apr 2, 2022 · 5 comments

Comments

@jacob-thanh
Copy link

When I first installed and later updated this bucket through scoop, I got this error message:

The term: init-spicetify-config-and-apply.ps1 is not recognized as a name of a cmdlet, function, script ...

Basically it's not in path, and failed the rest of the installation process.

It seems that all the scripts from this bucket's scripts folder are not copied into where spicetify-cli is installed. I did a manually fix by copying all scripts into where it's needed, but each update is troublesome. So I submit a new issue.
This error may happened because there is another bucket (main) which also contains spicetify-cli, and this line in your spicetify-cli:

      "installer": {
        "script": [
            "...",
            "$null, $bucket = find_manifest($app)", <---
            "$bucketdir = Find-BucketDirectory($bucket)",
           "...", 
        ]
      } 

Without find_manifest($app, $bucket) specifying which bucket, it's set to default as main bucket, whose script folder does not contains necessary scripts like init-spicetify-config-and-apply.ps1, spicetify-apply.ps1, ... and the following line

    @(all the scripts) | ForEach-Object { Copy-Item "..." } ;

fail, never made it into spicetify-cli installation directory.
I suggest changing that line into

    "$null, $bucket = find_manifest $app 'spotify'",

as

     find_manifest($app, 'spotify'),

both will be passed as array into $app param.
I'm sorry for the verbosity, hope this help anyone who encounter the same problem as I did.

@rollingmoai
Copy link

rollingmoai commented Apr 3, 2022

@jacob-thanh See https://spicetify.app/docs/getting-started/advanced-installation#scoop. Spicetify is already in the official repos #65 (comment), do not use this bucket.

@Ama1999
Copy link

Ama1999 commented Jul 5, 2022

@TheRandomLabs You may want to consider cutting this package if the official repos contain spicetify in the same capacity, especially with the compile/install errors yours has? Just an idea.

@sitiom
Copy link

sitiom commented Jul 5, 2022

@Ama1999 TheRandomLabs has been absent for over a year, and everything here is just run by CI now. This is why the Nonportable bucket has been mirrored to the official org instead of being transferred (ScoopInstaller/Nonportable#1)

@Ama1999
Copy link

Ama1999 commented Jul 5, 2022

@sitiom Ah okay. Thanks for letting me know!

@sitiom
Copy link

sitiom commented Jul 5, 2022

As @itsmeboy0 suggests, I recommend just using spicetify-cli from the official buckets now. The spicetify-marketplace custom app is great and extensions/themes installed from there auto-update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants