I've now moved a few of my personal projects that used regular ol' #npm to the superior #pnpm. It was a bit of setup, and Github Actions erred out for a while until I figured out a fix, but all in all I think I'm better off. Thank you, #EmberJS project, for shining the light.
OK, I should really change all my projects that use #npm/#yarn to use #pnpm. If you barely use Node then it's probably not worth it, but for a webdev it now seems like a no-brainer.
Posted this on @astro#discord but maybe someone here can help?
I can't install a new #astro project by running "npm create astro@latest". Using #pnpm and #yarn works just fine.
#node version: 20.9.0 & #npm is 10.1.0. Tried installing #svelte with npm for comparison & got a similar error, so it's a local issue? When using "npm install" to install #11ty it works with no issues.
Could anyone point me to a direction how to fix this? I'm not very familiar with debugging these kind of things...
The most wtf moment happened to me today when I ran git add package.json pnpm-lock.yaml and it started installing packages, only to realise I actually typed pnpm instead of git.
Apparently both package.json and pnpm-lock.yaml are npm modules.....
I'm thinking about how I could a good #cli for #hsml
I may orientate on existing CLIs like #Rust, #deno or #pnpm
so e.g.
hsml compile # compiles all .hsml files to .html inside current folder and recursive below
hsml compile ./example.hsml # just compiles the given file
hsml fmt # formats
hsml fmt # just formats given file
hsml parse ./example.hsml # parses the given file and std::out as json AST
But I'm not sure if this fulfills all need or if I need to change something