SrBrahma
commented
3 years ago Done recall with @latest in 2.2.0
Open SrBrahma opened 3 years ago
SrBrahma
commented
3 years ago Done recall with @latest in 2.2.0
Quick soon todo/free thinking:
1)
Check gev version and recall with @latest if not latest already (as npx will unfortunatelly use old versions if available in cache)done in 2.2.02) Interactive menu to choose the flavor, project name, dest path (maybe)
npx gev? This would require removingtsas default flavor.npx gev tsalso have a interactive menu? Or onlynpx gev ts -iwould do it?3) Multiple common dependencies to be additionally installed. They could all be in the root, but could also be categorized. As my common deps wouldn't be the same as everyone else's and having all the deps showing there would be a huge pollution, there could be the common ones (like most popular ones), but also the user saved ones. This could also be set in the future user personal flavor. The user could also write the deps' names to add / find them (this is similar to the idea I sent to the vscode/typescript team on a seasonal form, and then to an extension idea I already had*). The main flavor (template) could still be the ts, but with the spices (those additional and specific configs). There could be an option in the interactive menu like
Use personal spiceand the user saved spices would show there. But maybe both concepts wouldn't be clear to separate one from the other. Anyway, the user flavors/spices would be accessible via local storage or github repo / gist. Just the username could be entered, and it would look for public repos (or private ones if logged) and the desired spice could then be selected, if multiple ones are present.There could be a user@ts template, but also a user@ts#expo. Maybe, just using user@ts would ask for the spice. user@ts# would use the default one the user has. Maybe it's getting more complex than it should.
* -> 4) I could do a gev extension for the VsCode. Instead of calling it by the terminal, it would also be possible to use it via GUI in vscode. Not really hard to do but as it certainly would translate to a cli call, I need the cli structure to be in its final form. It's all coming together!