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
I am currently useing rush with pnpm and I'm having a lot of packages in out monorepo.
Mostly angularcli projects. So when using rush, its linking all the node packages to the package root (container angular.json, pacakge.json, src\ folder etc. When I build my pacakge now, its placed in .\dist\ with all compiled files and correct resolution of all paths. But the package will always be linked to project\ instead of project\dist and according to rush developer, it can only be changed if pnpm would support change the linking-path.
Without this change, I would need to "extend" my package-root package.json with types,main etc parameter that are not required there, and some package will fail anyways because of bad angular behaviour?!
From my understanding, adding an option to change pnpm linking destination would allow to extend the linking system in rushjs, so I can make it point to any project/dist or whatever folder I need to be linked to.
Describe the drawbacks of your solution
So far, as its an additional option, I dont see any drawbacks if unused.
Describe alternatives you've considered
I haven't
The text was updated successfully, but these errors were encountered:
Describe the user story
I am currently useing rush with pnpm and I'm having a lot of packages in out monorepo.
Mostly angularcli projects. So when using rush, its linking all the node packages to the package root (container angular.json, pacakge.json, src\ folder etc. When I build my pacakge now, its placed in .\dist\ with all compiled files and correct resolution of all paths. But the package will always be linked to
project\
instead ofproject\dist
and according to rush developer, it can only be changed if pnpm would support change the linking-path.Without this change, I would need to "extend" my package-root package.json with types,main etc parameter that are not required there, and some package will fail anyways because of bad angular behaviour?!
Please see issue: microsoft/rushstack#728
Describe the solution you'd like
From my understanding, adding an option to change pnpm linking destination would allow to extend the linking system in rushjs, so I can make it point to any
project/dist
or whatever folder I need to be linked to.Describe the drawbacks of your solution
So far, as its an additional option, I dont see any drawbacks if unused.
Describe alternatives you've considered
I haven't
The text was updated successfully, but these errors were encountered: