Documentation not up-to-date for "Install actions"

[schorfES]

Since version 5.0.0 the Install action is deprecated and is not included by default to the generator instance. This is currently not documented/reflected in here:

• https://yeoman.github.io/generator/Generator.html#installDependencies
• https://yeoman.io/authoring/dependencies.html

[GregorBiswanger]

How is that best to be solved now? I urgently need an npm install solution. Tonight I have a live stream and wanted to show my viewers Yeoman with TypeScript.

[GregorBiswanger]

Okay, I saw that it then installed automatically. It reports that no standard package manager has been stored and that it uses npm. How can you fix a package manager like yarn here?

In principle, can the install method also be viewed as deprecated?

The TypeScript Type Definitions would also have to be adapted. Here npmInstall methods etc. are also offered.

[fernandopasik]

According to the 5.0.0 changelog there should be a way to access:

this.addDependencies({lit: '2.0.0'})
this.addDevDependencies({mocha: '8.4.0'})

[mshima]

Background about this change: #1283.

Force yarn using cli:
yo --node-package-manager yarn

Force yarn inside a generator:
this.env.options.nodePackageManager = yarn;

[GregorBiswanger]

We have created a generator that is supposed to create a new project directory with package.json. Only npm install will then not be executed automatically. Only if the package.json is created in the current directory where the generator is being executed. We tried this.destinationRoot(this.answers.kataname);

Although it shows during the debug that it has found the package.json, no installation is started.

Please urgently need a solution.

This is the generator:
https://github.com/GregorBiswanger/generator-create-kata

[mshima]

In that case you should set the environment cwd this.env.cwd = this.answers.kataname; too.
Or execute yarn using a custom install task:

generator/lib/index.js

Lines 127 to 128 in 84551ee

	* @property {boolean|Function} customInstallTask - Provides a custom install task. Environment >= 3.2.0
	* Environment built-in task will not be executed

Something like:

constructor(args, opts)
  super(args, opts, {customInstallTask: preferredPm => this.spawnCommandSync(`${preferredPm} install`)});
}

Edit:
Updated to use preferredPm

[GregorBiswanger]

We use npm :)

Thanks for your help!

[fernandopasik]

The TypeScript Type Definitions would also have to be adapted. Here npmInstall methods etc. are also offered.

@GregorBiswanger the definitions were updated a few hours ago
DefinitelyTyped/DefinitelyTyped#52666

[GregorBiswanger]

@mshima Unfortunately the cwd assignment does not work. He then runs npm install from global user profile c:\user\name. Although CWD gets the correct path:

    async prompting() {
        this.answers = await this.prompt(...

        const destinationRoot = this.destinationRoot(_.kebabCase(this.answers.kataname));
        this.env.cwd = destinationRoot;
    }

[gbrlmngr]

Any update on this?

I can't, for the life of me, find a way to configure installDependencies.
this.installDependencies always errors out with is not a function.

And also, I just cannot find a way to disable the unchanged package.json message (No change to package.json was detected. No package manager install will be executed.).