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
Is your feature request related to a problem? Please describe.
It would be nice if NativeScript worked with pnpm without --shamefully-hoist, as that flag disables the isolation and strictness of packages that pnpm otherwise grants, and makes NativeScript incompatible with pnpm workspaces as it likely assumes on where the hoisting happens and workspaces generally don't use or want to use that flag.
Describe the solution you'd like
Support pnpm without --shamefully-hoist.
Describe alternatives you've considered
Give up and use it with the flag outside a pnpm workspace, wiring the internal packages some other way.
Anything else?
shamefully-hoist = true can be included in a project level .npmrc for users running pnpm install directly so they don't have to remember including that. It can also be generated by the CLI when using pnpm or suggested to be added by it if it is missing.
Is your feature request related to a problem? Please describe.
It would be nice if NativeScript worked with pnpm without
--shamefully-hoist
, as that flag disables the isolation and strictness of packages that pnpm otherwise grants, and makes NativeScript incompatible with pnpm workspaces as it likely assumes on where the hoisting happens and workspaces generally don't use or want to use that flag.Describe the solution you'd like
Support pnpm without
--shamefully-hoist
.Describe alternatives you've considered
Give up and use it with the flag outside a pnpm workspace, wiring the internal packages some other way.
Anything else?
shamefully-hoist = true
can be included in a project level.npmrc
for users runningpnpm install
directly so they don't have to remember including that. It can also be generated by the CLI when using pnpm or suggested to be added by it if it is missing.Please accept these terms
The text was updated successfully, but these errors were encountered: