Currently we set up a discrete folder for configure and controller when running the pie install, we need to see if this is still required as it causes issues when the pie root/configure/controller depends on the same dependency and you want to link them.
so if i have a pie like so:
dependencies: {
'my-comp': '1.0.0'
}
and a configure package like so:
dependencies: {
'my-comp': '1.0.0'
}
When we install this - we get the same package installed in 2 locations - one in .pie/node_modules and one in .pie/.configure/node_modules .. if you want to set up linking then - you have to remember to set up 2 links, or remove the one in .configure so that the one in .pie gets resolved.
Currently we set up a discrete folder for
configureandcontrollerwhen running thepie install, we need to see if this is still required as it causes issues when the pie root/configure/controller depends on the same dependency and you want to link them.so if i have a pie like so:
and a configure package like so:
When we install this - we get the same package installed in 2 locations - one in
.pie/node_modulesand one in.pie/.configure/node_modules.. if you want to set up linking then - you have to remember to set up 2 links, or remove the one in.configureso that the one in.piegets resolved.relates to #141