-
Notifications
You must be signed in to change notification settings - Fork 19
Description
My Initial Install
I tried to upgrade my working initial publish-spa 0.2.0 setup and the former logseq static bild using logseq 0.9.8.
but I got a broken install and never back to work.
I used the instruction at https://github.com/logseq/publish-spa?tab=readme-ov-file#cli currently still published in branch main for Release 0.3.0 , edf2903
Prerequisite: yarn was upgraded globally to version 3.7 after the initial install for other purposes! ( I am not familiar with fully isolated installs using yarn!), the working install was issued under yarn v1.22.19.
Deleting the publish-spa git checkout and the containing static logseq build and starting from scratch ended up with the same resulting errors below.
I now used again:
- delete publish-spa git cloned folder
- recreate folder
- babashka and clojure installed! (bb -> Babashka v1.3.186 REPL, clj -> Clojure 1.11.1)
-
git clone https://github.com/logseq/publish-spa cd publish-spa && yarn install - output
➤ YN0070: Migrating from Yarn 1; automatically enabling the compatibility node-modules linker 👍 ➤ YN0000: ┌ Resolution step ➤ YN0000: └ Completed in 4s 382ms ➤ YN0000: ┌ Fetch step ➤ YN0013: │ wrap-ansi@npm:2.1.0 can't be found in the cache and will be fetched from the remote registry ➤ YN0013: │ wrappy@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry ➤ YN0013: │ y18n@npm:4.0.3 can't be found in the cache and will be fetched from the remote registry ➤ YN0013: │ yargs-parser@npm:11.1.1 can't be found in the cache and will be fetched from the remote registry ➤ YN0013: │ yargs@npm:12.0.5 can't be found in the cache and will be fetched from the remote registry ➤ YN0000: └ Completed in 3s 366ms ➤ YN0000: ┌ Link step ➤ YN0000: └ Completed in 0s 227ms ➤ YN0000: Done in 7s 984ms - command
Error:
yarn global add $PWDUsage Error: The 'yarn global' commands have been removed in 2.x - consider using 'yarn dlx' or a third-party plugin instead $ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0] <scriptName> ...
No idea of the purpose of yarn global add $PWD and how to replace the functionality