when I invoke yo from command palette

I noticed that your extension (probably Yo itself) is calling process.exit() at some point. I know some node JS libraries tent to abuse process.exit() as a way to do flow control in their program. I see this happening when I abort Yo after it found a conflict when applying file changes.

In the future VS Code will ignore process.exit() calls because otherwise the extension host goes down and you would have to restart VS Code.

I wonder how Atom behaves here I am sure they have the same problem, do you happen to know?

Not sure you can do anything about it but if Yo claims to be pluggable, they must also provide a way to avoid process.exit(). In fact, they should not even use it at all.

It is possible to run Yo in VS Code when no folder is opened. In that case I suggest to either ask the user for the destination of where to install the generated files to or just inform that you first need to open a folder.

I would actually like to always be asked from where to run the generator (cwd) so that I am in charge where to install the generated files to. Currently it feels a bit weird that the files end up in my current workspace in a sub folder.

Is this project available as an npm package and does it support some sort of command extensibility?

I am tinkering with an idea to generate project scaffolding as one liner (similar to #40).
E.g: aspnet new (instead of yo, aspnet, console app)

ofcourse, such simple verbs may not encompass all the wide range of template options, but for my use case I'm happy with these terse one liners.

so, i was wondering if i could somehow add this package as a dependency and extend on top of this? Would uploading to npm as a package work for you in that case?

A password input is now shown as a normal input. Add support for this by using the password property in the options object.

After extension installation no generators displayed.

I tried to reinstall extension, but nothing helps.

Visual Studio Code
Version 0.10.1
Commit df352367df2efcfa9d602d471e4e2f42140a0f05
Date 2015-11-17T15:25:33.342Z
Shell 0.34.1
Renderer 45.0.2454.85
Node 4.1.1

yo 0.4.0

I am running in a type error as shown below and believe that's because vscode-yo doesn't return a promise from prompt but yeoman-generator expects that

Uncaught Exception:  TypeError: Cannot read property 'then' of undefined
TypeError: Cannot read property 'then' of undefined
    at Base.prompt (/Users/jrieken/Code/collab/generator-code-javascript/node_modules/yeoman-generator/lib/base.js:240:44)
    at prompting (/Users/jrieken/Code/collab/generator-code-javascript/generators/app/index.js:111:21)
    at Object.<anonymous> (/Users/jrieken/Code/collab/generator-code-javascript/node_modules/yeoman-generator/lib/base.js:439:23)
    at /Users/jrieken/Code/collab/generator-code-javascript/node_modules/run-async/index.js:26:25

At the moment when executing a generator within VSCode with vscode-yo, the root folder used by the generator is the project's root folder. It would be interesting to be able to use the current selected folder in the source explorer so that my generator doesn't have to know the target folder structure to generate items at the correct place.

For instance I have the following project struture opened in VSCode:

Root
|- src
| |- home
| |- about
|- test
| |-etc

I want generated files to endup within a custom folder structure under the src folder.

The execution folder is always Root when running a generator. Therefore I have no other choice than handle in my generator the fact that I have to add an extra src folder. But then what about other projects structures where they have a different hierarchy?

It'd be nice to use the currently selected folder in Source Explorer as the generator's execution folder.

Add a Yeoman icon for the VS Code Gallery.

If a file already exists, people can show the difference between the actual and the expected file. It would be nice to handle this properly.

We'd like to hook up a Yeoman generator so that users of the PowerShell extension can easily create new PowerShell projects. What do we need to do have our generator show up in the quick pick list?

Does your generator resolution depend on the workspace itself having a package.json file with the generator installed as a dependency? Is there any way that our extension could include the generator so that it shows up in the list without the workspace needing a package.json?

Thanks!

cc @rkeithhill

The plugin does not execute a new generator if the user pressed escape in the previous flow.

When the user starts a new generation and presses esc at some question, the flow is stopped. When he triggers a new generator, the environment is executed correctly on line 67, but the prompt method is not fired.

Does this have something to do with not calling the callback here?

generator-nm uses this.appname as default application name. The first time the generator is executed, the app name is empty. When quitting the generator (by pressing escape) and running generator-nm again, the app name is correct.

The adapter is just getting the question here.

When I put a breakpoint here, the first question in the array is

{
    "default": "",
    "filter": x => _s.slugify(x),
    "description": "What do you want to name your module?",
    "name": "moduleName"
}

The second time I run the generator, the default value is correct.

{
    "default": "yo-test",
    "filter": x => _s.slugify(x),
    "description": "What do you want to name your module?",
    "name": "moduleName"
}

Any idea how this is possible? @sindresorhus @SBoudrias

Currently we only support lists with object values like {name: 'foo', value: 'bar'}. PR #49 will add string support as well. But according to the docs of Inquirer.js, we will have to add support for some others as well.

choices: (Array|Function) Choices array or a function returning a choices array. If defined as a function, the first parameter will be the current inquirer session answers. Array values can be simple strings, or objects containing a name (to display in list), a value (to save in the answers hash) and a short (to display after selection) properties. The choices array can also contain a Separator.

So this is what should be done, and what we already have

• Support functions
• Support strings (#49)
• Support objects
• Add support for separator (do not show them)

@SBoudrias Sorry for the interruption but could you explain what that short is? When is it shown? For instance if we had a list of one item [{name: 'foo', value: 'bar', short: 'fb'}]. How does/should that render?

// @zuoez02

This is primarily for development purposes. Setting npm link to a local working directory allows for local development . Would be nice to be able to do something like yo link c:/foo/foobar/fooprojectdir and then when you go yo again the local yeoman project would be available.

Inquirer.js supports this.async() in most of its functions.

default, choices (if defined as functions), validate, filter and when functions can be called asynchronously using this.async(). You just have to pass the value you'd normally return to the callback option.

Only when is supported for now.

More info #26

I have VS Code 1.7.2 and the Yo extension 0.9.3 installed. I also have few generators installed. However, when I try to invoke yo it complains with the following message:

Make sure to install some generators first.

Trying yo command in a terminal does give me generators available.

Is this a known issue?

Thanks!

First extension I installed in vscode. The instructions are very vague though, it doesn't mention if I have to install generators first or...
I do have a Bootstrap generator I never use, but it's there, and when I run yo in vscode I get this:

When I use within VS Code, the extension works but it does not show the npm install progress that happens. Is this a known issue? I tested this with multiple generators and got the same.

Thanks!

Now the user has to press esc to continue, but that's weird off course. Better would be to add an extra element to continue and quite if the user presses esc

It's possible to only prompt for questions depending on the answer of other questions. This can be done with the when function.

At this moment, the when function is being ignored.

Hi, this extension is awesome!

For some reason, it's not working with the fountain-angular2. It's not showing the generator and its sub-generators either.

I'm not sure what is going wrong....

Instead of an empty picker.

findup is faster then findup-sync.

Noticed this today, when I open Yo, it shows the picker, opens the output panel and then seems to open the picker again? Is this because of focus issues? If so, there should be API to open the panel without passing focus into it.

See: https://github.com/SBoudrias/Inquirer.js#question for the spec. This is preventing some generators from working as they rely on the given answers to calculate a default.

It will be possible in the future to show a progress bar when options are loading. It would be very nice to do this when the generators are being loaded.

generator-aspnet has quite a useful sub generators, it'd be useful to be able to run those from within Code.

Any reason why the postinstall script is not configured for package.json:

"postinstall": "node ./node_modules/vscode/bin/install"

If you do not use this, otherwise the vscode module cannot be resolved because vscode.d.ts is missing unless you have this postinstall script.

Is it possible to support entering a one-liner to scaffold?

For example: yo aspnet:MvcController MyController

Currently I do

yo ENTER
aspnet ENTER
MvcController ENTER
MyController ENTER

As per #3 (comment), multiselect does not work when values are simple strings. Currently vscode-yo only supports objects.

// @dermeister0

I'm seeing that with nvm to manage nodejs/npm installations, vscode-yo when invoked says "install some generators first".
I'm confident my generators are alright because they seem to work when invoked from command line. So, it looks like vscode-yo couldn't find npm install path?

with nvm, my npm path is no longer at %USERPROFILE%\AppData\Roaming\npm but its at %USERPROFILE%\AppData\Roaming\nvm\v7.6.0\

Is this a known issue or do i need to change some default setting to get this to work. Please help.

I think it would be a nicer experience if the resolving of available yo-generators and the loading of a specific generator happens without the picker closing all the time and then reopen after a second or so.

You can always add a promise into the picker API and you will get progress while you resolve the things in the background.

If the user presses the Esc, it is handled as an enter keypress at the moment. This is due to a bug in VSCode where you can't determine the difference between an empty input field + enter and an Esc keypress. They will fix it in the next build.

Use read-pkg-up to retrieve the generators instead of find-up.

Hi there,

The SharePoint Yeoman Generator to scaffold web part projects is currently into a npm scope, which means, I will have to run the yo as:

yo @microsoft/sharepoint

Does the yo extension support this? When I use the extension in VS code, it just shows sharepoint as the generator and not @microsoft/sharepoint. The next step of showing sub generators also succeeds. But then once I select the default app sub-generator, it throws the following error:

You don't seem to have a generator with the name "sharepoint:app" installed.

The generator as such when used in the command line works without any issues.

Any help much appreciated.

Thanks,
Chaks

It might take some time before the list of available generators pops up. It would be nice to show a progressbar in the meantime.

Hi @SamVerschueren ,

First, great initiative to wrap yo inside the vscode!
I got a error when I use it, I will try to explain the scenario.

When I try to use generator-generator from vscode the following error:

Error this.async is not a function

Steps:

1. yo
2. generator
3. <enter, confirming the suggestion>
4. error presented: Error this.async is not a function

Using the normal yo works fine:

yo
? 'Allo GORSKI! What would you like to do? Generator

Make sure you are in the directory you want to scaffold into.
This generator can also be run with: yo generator

? Your generator name generator-exploratory-test-cases-yo
Your generator must be inside a folder named generator-exploratory-test-cases-yo
I'll automatically create this folder.
? Description 

Versions:
npm -v --> 3.3.12
node -v --> v5.3.0

When try generate asp.net Class not get options for name of Class but just run it without name of Class

Yo version 0.7.0

Only the write and writeln of the logger are directed to the output channel. We should write everything to the outputchannel to inform the user correctly.

It would be nice to ad color support for file diff (red for removed lines and green for added lines).

This is currently not supported by VS Code core.

At the moment, VSCode does not offer multi select prompts. It is implemented as a normal select at the moment https://github.com/SamVerschueren/vscode-yo/blob/master/src/prompts/checkbox.ts.

If VSCode releases multi-select, which they probably will in the next build. Use those native multi-selects instead.

Add a progress bar somewhere to indicate that yeoman is installing dependencies.

This only seems to work in certain cases. It fails when trying to generate a sub-generator with generator-generator.

generator.runInstall('yarn', [], () => { generator.spawnCommandSync('npm', ['run', 'test']); });

When my generator fires these commands I silently fail through the plugin. Anyone know if I'm doing anything crazy? It works fine on my command line.

Because the new yeoman-generator expects a promise that resolves the answers, it doesn't look like I can escape decently out of a generator. Have to investigate this further.

Taking this from twitter to here, just to see what we can do!

I'd love to have a core npm module that wraps most of the functionality up, so that both atom and code can just pull from the same feature set.

Right now atom-yeoman has the following features:

• Generator Service
  • Allows package authors the ability to call a specific generator.
• yo command
  • Lists all generators
• Loads from various locations that generators can be found (in atom we can't trust some of the NODE paths, code may be very similar)
• Parses files added, removed, changed, etc, and forwards that onto the service (for package authors to react to those files).

Proposal

Thoughts and ideas below.

Node Module

• Generator class
  • Constructor
    • Accepts a factory function that takes a list of generators and returns a Promise<IGenerator[]> which resolves when the generator has been selected.
    • Accepts a factory function that takes an input question, and returns a Promise<IAnswer> which resolves when that question is completed.
      • This is where the editor specific package can inject it's UI elements.
    • Sets search locations, configurable using options.
  • Method for listing generators
    list(pathToDirectory: string, prefix?: string): Promise<IGenerator[]>
    • Search prefix (only list specific generators). Might not be required, can always be done after it returns.
  • Method for running a specific generator
    run(pathToDirectory: string, generator: string): Promise<IResult>
    Shortcut that calls generator.run() under the covers.

Example atom/code usage:

let yeomanService = new YeomanService((q: IQuestion) => showQuestionForUser(q));
yeomanService.list(process.cwd())
    .then((generators) => listGeneratorsForUser())
    .then(generator => generator.run())
    .then(result => doSomethingWithResult())

This would make it much simpler for people to use yeoman in an electron like application, so it may have uses outside of just atom/code.

Atom

Has CSP issues, there are clear work around that is already handled. Hopefully this could be handled outside of the node module, so we don't have to worry about the nasty CSP code everywhere.

Code

Not sure if CSP is enabled, it's entirely possible it is not currently enabled.

PR coming...

When I press F1, type in 'yo' then [Enter] I get the following Exception:

Uncaught Exception:  TypeError: Cannot read property 'split' of undefined
TypeError: Cannot read property 'split' of undefined
    at new Range (C:\Users\Anthony\.vscode\extensions\samverschueren.yo-0.8.4\node_modules\semver\semver.js:720:19)
    at outside (C:\Users\Anthony\.vscode\extensions\samverschueren.yo-0.8.4\node_modules\semver\semver.js:1123:11)
    at Function.ltr (C:\Users\Anthony\.vscode\extensions\samverschueren.yo-0.8.4\node_modules\semver\semver.js:1111:10)
    at C:\Users\Anthony\.vscode\extensions\samverschueren.yo-0.8.4\out\yo\yo.js:37:49
    at Array.map (native)
    at Yeoman.getGenerators (C:\Users\Anthony\.vscode\extensions\samverschueren.yo-0.8.4\out\yo\yo.js:25:21)
    at C:\Users\Anthony\.vscode\extensions\samverschueren.yo-0.8.4\out\extension.js:90:37
    at Environment.resolver.lookup (C:\Users\Anthony\.vscode\extensions\samverschueren.yo-0.8.4\node_modules\yeoman-environment\lib\resolver.js:50:12)
    at Immediate._onImmediate (C:\Users\Anthony\.vscode\extensions\samverschueren.yo-0.8.4\out\extension.js:89:33)
    at processImmediate [as _immediateCallback] (timers.js:374:17)

Digging in the code led me to the following line in yo.js: 37 :
=> generatorMeta.isCompatible = semver.ltr('0.17.6', generatorVersion);
generatorVersion's value is ~0.20.3

I had to patch the offending code in semver to handle the case where range object is null with a (range||'') to get it working (L720):

I also tried to upgrade semver to the latest version (5.1.0) but with no luck.

Feel free to let me know if you need further details.