pkgx
pkgx copied to clipboard
Example not working
sh <(curl tea.xyz) https://github.com/teaxyz/cli
Is returning
error: http (spilt-tea-404)
400: https://raw.githubusercontent.com/teaxyz/cli
While in the README.md
we can see this written.
Oh I should have removed that as didn't manage to implement in time.
Oh well, I guess this means I need to implement it today. Gimme a few…
Though this particular usage would be hilarious since it will essentially run sh <(curl tea.xyz)
after cloning tea/cli :D
I'm not sure if executable markdown works yet. If it's supposed to, I get this error. I don't know why it's looking in /opt for tea.xyz. My prefix is /opt/tea.
> echo $TEA_PREFIX
/opt/tea
> tea https://github.com/magnusviri/tea-notes/blob/main/README.md
tea: README.md downloading
panic: split tea. we’re sorry and we’ll fix it… but you have to report the bug!
https://github.com/teaxyz/cli/issues/new?title=panic%3Anot-found%3Asrcroot
----------------------------------------------------->> attachment begin
Error: not-found:srcroot
at file:///opt/tea.xyz/src/v0.13.0/src/hooks/useVirtualEnv.ts:34:15
at useVirtualEnv (file:///opt/tea.xyz/src/v0.13.0/src/hooks/useVirtualEnv.ts:35:7)
at abracadabra (file:///opt/tea.xyz/src/v0.13.0/src/app.exec.ts:163:25)
at async exec (file:///opt/tea.xyz/src/v0.13.0/src/app.exec.ts:12:72)
at async file:///opt/tea.xyz/src/v0.13.0/src/app.ts:30:9
<<------------------------------------------------------ attachment ends
I have been trying to build a package and I noticed this output. The TEA_PREFIX is certainly set ("/opt/tea"), but the PATH isn't getting the correct prefix ("/opt/tea.xyz").
+ export TEA_PREFIX=/opt/tea
+ TEA_PREFIX=/opt/tea
+ export MACOSX_DEPLOYMENT_TARGET=11.0
+ MACOSX_DEPLOYMENT_TARGET=11.0
+ export PATH=/opt/tea.xyz/var/pantry/scripts/brewkit:/usr/gnu/bin:/usr/local/bin:/bin:/usr/bin:.
+ PATH=/opt/tea.xyz/var/pantry/scripts/brewkit:/usr/gnu/bin:/usr/local/bin:/bin:/usr/bin:.
I symlinked /opt/tea.xyz to /opt/tea/tea.xyz and it still gets the same error.
I just figured out why the paths are the way they are. I submitted another issue about it. I think it's unrelated to this issue.
These examples have been removed. We may still add the feature where you can run commands against a repo. Maybe. Feels a little out of scope.