Open aarmn opened 2 years ago
+1 for this one, it'd be great
Although @aarmn I think it should be under nodePackages, because there are already plenty of tools in there, like tailwindcss
and a lot of the JS-based LSP servers
Although @aarmn I think it should be under nodePackages, because there are already plenty of tools in there, like
tailwindcss
and a lot of the JS-based LSP servers
Yup, but it's a non-dev, non-lib utility, so the case is similar to poetry pkg for python (I think it makes more sense to pkg this without namespace, maybe even more than poetry), It's end-user enough to doesn't matter its node and make sense not to be there, but I let the final decision be taken by the people who take the task and do it.
+1, but since the project uses pnpm
, we have to wait for #231513
I haven't been succesful in using yarn2nix
with slidev
yet.. and I am no JS expert but when I do something simple like:
npm init slidev
It gives you an option to choose npm
, yarn
, or pnpm
.
So do we still need to wait on #231513 ?
Project description Presentation Slides for Developers
Metadata It's a npm package, I guess that would make it easier to package, but its a tool, not a lib, so i think it should be package like poetry directly under nixpkgs and not nodePackages