Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open yeoman store to another Vinyl Adapter #720

Closed
Robertj-1 opened this issue Dec 9, 2014 · 1 comment
Closed

Open yeoman store to another Vinyl Adapter #720

Robertj-1 opened this issue Dec 9, 2014 · 1 comment

Comments

@Robertj-1
Copy link

Great idea to migrate yeoman file manager to vinyl mechanism.
But It would be very useful (at least for me) to allow to set its own vinyl adapter (rather than use vinyl-file).

To give you a rough idea of the use case we are thinking about, we would be really interested in being able to embed our Yeoman generators on our site in order to scaffold web and mobile applications from a definition manifest.
Online integration is important so that users can have a great user experience. An approach similar to
initializr where the user can point and click through the configuration and download a zip at the end of the process.

We followed your pointers given into another post and a few advice from Simon Boudrias.
So, we managed to poc a web node module that embeds yeoman environment and our custom generators.
To add to our experimentation, this node module is hosted by Microsoft Azure ("Path too long" barrier).
So, to achieve our prototype, we want to use another file system mechanism.

It seems that everything is already present to accomplish this. A priori, it's enough to change two methods in mem-fs module (vinylFile.readSync, path.resolve).
These methods will be delegated to a third vinyl adapter

To talk about another use case, it would be interesting for generators to allow use template files hosted online (bootstrap themes...), and provides a mechanism such as office themes.

I hope that my suggestion will retain your attention.

Good continuation !

@github-actions
Copy link
Contributor

github-actions bot commented Jan 2, 2020

This issue is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot added the stale label Jan 2, 2020
@github-actions github-actions bot closed this as completed Jan 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants