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
buildDescribes issues related to build operationsdebugfeaturepreviewDescribes issues related to preview commandrunDescribes issues related to run command
Describe the solution you'd like
Please add support for pnpm
pnpm uses hard links and symlinks to save one version of a module only ever once on a disk. When using npm or Yarn for example, if you have 100 projects using the same version of lodash, you will have 100 copies of lodash on disk. With pnpm, lodash will be saved in a single place on the disk and a hard link will put it into the node_modules where it should be installed.
The text was updated successfully, but these errors were encountered:
@rosen-vladimirov did you make any progress on this? I use pnpm for all my N apps but I am facing issues when using some tns commands whic force the use of npm. Could we simply have a option or something to set the actual "npm" command to be run for install. For me for example it would be "pnpm i - - shamefully-hoist"
Hey @farfromrefug ,
We've not worked on this feature request. One way to implement it is to add a new package manager support in NativeScript CLI, similar to the way yarn is supported. To achieve this you'll have to provide an implementation similar to these ones:
buildDescribes issues related to build operationsdebugfeaturepreviewDescribes issues related to preview commandrunDescribes issues related to run command
Describe the solution you'd like
Please add support for pnpm
The text was updated successfully, but these errors were encountered: