Skip to content

Bug report: spfx project upgrade order incorrect #6602

@cwdata

Description

@cwdata

Priority

(Low) Something is a little off

Description

When you update the npm packages following the order provided in the generated output from 'spfx project upgrade' you get an error when trying to install the dev dependency @rushstack/eslint-config. This happens with upgrades to 1.18.2 and to 1.20.0 (haven't tested others).
The problem is, that the new version of eslint has to be installed before eslint-config.
So the order of the steps in the generated output needs to be changed to first upgrade eslint and then @rushstack/eslint-config.

Steps to reproduce

Upgrade a project from spfx 1.18.2 to 1.20.0 exactly following the single steps in the order provided by the output from spfx project upgrade.
=> Error when executing 'npm i -DE @rushstack/[email protected]'

Expected results

When doing the upgrade one step at a time, no errors should be thrown.

Actual results

See above.

Diagnostics

No response

CLI for Microsoft 365 version

v10.3.1

nodejs version

v18.19.1

Operating system (environment)

Windows

Shell

PowerShell

cli doctor

No response

Additional Info

No response

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions