Hi @@JenWilson82653, thanks for reporting this.
Unfortunately, this issue is not caused by Angular, but rather StackBlitz as their project structure is slightly different from that of the standard ng new and has invalid configuration in angular.json.
We'll try to reach out to StackBlitz to get this sorted. Apologies for the inconvenience.
Hey all- I'm digging into this now, will circle back once I've ID'd the root issue. Should be able to get a fix in shortly
Thanks for your quick action. Feel free to ping me on slack if you need any help @EricSimons.
Awesome, thanks @alan-agius4!
I spent the past hour or so investigating and I think I've figured out the core issue- seems like it's a bug in our project scaffolding/downloading logic. I'm going to put together a fix first thing tomorrow, test on staging and then deploy to prod. Will circle back here once it's live to confirm all looks good on your end 馃憤
Update: Ended up getting tied up today, targeting EOD tomorrow though 馃槗
This is now live on prod and should be good to close! 馃挜
Thanks @EricSimons for the quick turnaround. I tried this and it seems to be working great.
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
_This action has been performed automatically by a bot._
Most helpful comment
Hey all- I'm digging into this now, will circle back once I've ID'd the root issue. Should be able to get a fix in shortly