You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
yarn global add $PWD
Error:
Usage 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
The text was updated successfully, but these errors were encountered:
(I replaced the --frozen-lockfile option due to a hint from executing this option. The result was both the same:
YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: ┌ Post-resolution validation
➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
➤ YN0000: └ Completed
➤ YN0000: Failed with errors in 6s 635ms
Hi. I'm still using yarn 1.x but will let you know if I come across this when I upgrade. In the meantime, npm i -g also works to build the CLI. I've updated the docs to mention this
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:
No idea of the purpose of
yarn global add $PWD
and how to replace the functionalityThe text was updated successfully, but these errors were encountered: