It is still very basic but it provides an idea of direction of travel.
I am not quite sure I understand the question, but in general, the implementation was quite simple as the current state of packages is available in the package.json file.
I also aim to have the ability to add dependency import statements to elements via the new item wizard and via right-click context commands. A small feature, but it makes sense to me.
Yes, this is something that I have considered, or at least similar to. It would be relatively simple achieve if the model used to describe the site structure and dependencies is formalised. This model could then be populated, serialised and saved by the user for a later date. To use it as a basis for a new project an OpenFileDialog (or something similar) can be used to select a previously saved .json file, then push that through the same service that generates the a project. This is not actually that far away as things stand.
@HamedFathi Yes. This will be the next update. I have to admit that I have not yet installed VS 2019. I like to keep my system as stable and fast as possible.
Both Visual Studio 2017 and 2019 should now work via the same download.
There is now a file format check for saved project template files.
There was not much at all required to change in order to enable both versions of Visual Studio to be served from the same extension, only some package conflicts.
A new Visual Studio Aurelia template with no CLI dependency
Very lightweight and fast
A few miscellaneous bug fixes
I was aiming for a fast light-weight and transparent template that provides fast performance.
The video shows a new project with very basic navigation, adding pages and other elements followed by publishing to a stand alone self hosting site in a little over 4 mins and 4MB.