`aspire restore` should be auto-run for TS apphost apps after `aspire new`

[DamianEdwards]

Right now, if you aspire new to create a new TS apphost (Express/React or empty) and then immediately open the created app in VS Code, you get squiggilies in the editor due to missing generated modules. If you manually run aspire run or aspire restore yourself it fixes itself.

[MihuBot]

I'm a bot. Here is a possible related and/or duplicate issue (I may be wrong):

• After creating a new TS starter, we should automatically run aspire restore #15169

[DamianEdwards]

Hmmm it seems this was supposed to be done as part of #15169 but I'm not seeing that using latest 13.2 build today

[joperezr]

After doing some local testing, I realized that aspire restore is indeed running after doing aspire new, the problem is that it seems that it is not reading aspire.config.json file and not restoring additional integrations listed in the packages property, which is what is causing the behavior that Damian is seeing. This is because the template he is picking (Express) depends on the Aspire.Hosting.JavaScript integration for the AddNodeApp method, but I can see that restore did happen after aspire new, but it doesn't restore the package until I manually run aspire restore or aspire run a second time.