|
Top-level
 When I got this error last night I was like "ha ha, what a silly small error" and figured this morning I'd get up and work it out I CAN'T WORK IT OUT It fails saying it can't open a file. It will not say what file. pnpm link is doing nothing for me at all. i cannot inject a console.log to print the file it's trying to open I tried strace. strace does not show opening a file!!! I thought this was going to take minutes and I've been poking on and off all day :( 6 comments
How does `npm link` interact with npm workspaces? I want to `npm link` (pnpm link but whatever) an on-disk npm package A into a local project B. However, "A" is a sub-package ( like, a workspace package https://docs.npmjs.com/cli/v7/using-npm/workspaces ) of another package "C". The npm repository entry for A https://www.npmjs.com/package/@atproto/pds just links to C. So: If I want to make B use the on-disk version of A, do I `pnpm link` A? or C? Or both? Returned to debugging this this morning, but suddenly was unable to get it to print the error message any message. After a certain amount of fiddling, believing I did not understand how systemd services worked, I discovered that in fact at some point during the debugging I actually fixed the error, thus resulting in the error message no longer printing. Unfortunately I continued debugging after the point at which it started working and in the process I managed to break it again Incidentally an interesting thing I've learned reading the docs is that BlueSky significantly relies on CBOR. This is a reasonable choice but makes me *very* curious whether any part of the BlueSky stack is susceptible to duplicate key attacks. I have found it… the next evolution of curl | sudo sh https://github.com/bluesky-social/pds/blob/main/pdsadmin.sh Shell script that takes a subcommand, downloads a script by the name of the subcommand from github, then executes it as root |
Gregory's Server
Is pnpm link different from npm link?